Re: no printing cache info

2010-11-28 Thread Mark Kettenis
Date: Sun, 28 Nov 2010 17:02:43 +1100 (EST) From: Damien Miller d...@mindrot.org On Sat, 27 Nov 2010, Ted Unangst wrote: if you really really need to know that your cpu cache has 48 fully associative entries, go consult the spec sheet. otherwise, save some electrons. or, how

Re: no printing cache info

2010-11-28 Thread Ian Darwin
Best thing would be to print it once per socket, i.e. for the first core of each physical CPU. Oh, and the flags can be subtly different for other CPUs in the system, even if they are exactly the same model, because the BIOS can enable/disable some features. Yes to the first, and the

Re: no printing cache info

2010-11-28 Thread Philip Guenther
On Sun, Nov 28, 2010 at 7:57 AM, Ian Darwin i...@darwinsys.com wrote: Best thing would be to print it once per socket, i.e. for the first core of each physical CPU. Oh, and the flags can be subtly different for other CPUs in the system, even if they are exactly the same model, because the

Re: no printing cache info

2010-11-28 Thread David Gwynne
i agree with mark. On 28/11/2010, at 11:12 PM, Mark Kettenis wrote: Date: Sun, 28 Nov 2010 17:02:43 +1100 (EST) From: Damien Miller d...@mindrot.org On Sat, 27 Nov 2010, Ted Unangst wrote: if you really really need to know that your cpu cache has 48 fully associative entries, go

Re: no printing cache info

2010-11-27 Thread Damien Miller
On Sat, 27 Nov 2010, Ted Unangst wrote: if you really really need to know that your cpu cache has 48 fully associative entries, go consult the spec sheet. otherwise, save some electrons. or, how about only print this (and flags) for the first attached CPU? Unless there are plans to support