Date: Mon, 09 Nov 2015 10:39:31 -0700 From: Ian Lepore <ian@freebsd.org> To: Adrian Chadd <adrian@freebsd.org>, Eugene Grosbein <eugen@grosbein.net> Cc: "freebsd-mips@freebsd.org" <freebsd-mips@freebsd.org> Subject: Re: CPU underload Message-ID: <1447090771.91534.477.camel@freebsd.org> In-Reply-To: <CAJ-Vmon=GwJhUaoS=AH5iOzEAdUUEcCz9%2BW6jdPq3h1TyXZ_3A@mail.gmail.com> References: <56348063.3090508@grosbein.net> <56348239.3050701@grosbein.net> <CAJ-Vmok%2BgKXcpzpxNCBhxX8sYSh%2BQO7OaeojB4MCufO%2BA4zceg@mail.gmail.com> <563500FC.8020201@grosbein.net> <CAJ-Vmo=EpmG6OJxq_v_mqKMF48h_B3K7vKqnnaKAi3x1s-uaWQ@mail.gmail.com> <5635148B.2070307@grosbein.net> <CAJ-VmomzkG8ZB0h1Qc=Oeny2ZOzQg1UirUprM_gmMy64F5ZRYw@mail.gmail.com> <56351AA6.80903@grosbein.net> <CAJ-VmomLen5p7ELejU7QtC5CO2j8hydb_CvdOqQsfaaMAtmdkA@mail.gmail.com> <563523CA.3040207@grosbein.net> <CAJ-Vmonpd8R5C%2BNvhOGFD1okkkit990DV8c4Dm%2BLmpZ2uFfVkA@mail.gmail.com> <56367686.4090801@grosbein.net> <CAJ-VmomtJ9eKfAJYfn4e2S1xWN8-YHo0M0KH-9V=VjNBf6vVVA@mail.gmail.com> <563707A0.3040700@grosbein.net> <CANCZdfrB0hkjmTU-9NzimBv=X_h-=bF0D2azBxg=9B=kmitv7Q@mail.gmail.com> <56370E1D.3040801@grosbein.net> <CAJ-Vmo=0vOAq8db_GeLWmdXr7xJdzUh44ZZJrQ9vVdpvzT9hiQ@mail.gmail.com> <563F5630.2000407@grosbein.net> <CAJ-Vmon8_kHeg3FOzK6T8amzF=-0ia0-Hb1ve2zZoEdgxrHO8g@mail.gmail.com> <563F938B.3070707@grosbein.net> <CAJ-Vmon=GwJhUaoS=AH5iOzEAdUUEcCz9%2BW6jdPq3h1TyXZ_3A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2015-11-08 at 11:23 -0800, Adrian Chadd wrote: > ok, what's the l1 cache size reported at boot up? > > I think I may just bump them all to 64. > > > -a 64 is not some kind of magic panacea. The value needs to be set to the cache line size for the runtime platform. If the right value is 32, then setting it to 64 will just waste memory. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1447090771.91534.477.camel>