From: Dave Jones <davej@redhat.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tossati <marcelo.tosatti@cyclades.com.br>
Subject: Re: Dave Jones: Fix cache size of Centrino CPU
Date: Wed, 1 Oct 2003 20:27:22 +0100 [thread overview]
Message-ID: <20031001192722.GF25612@redhat.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304AFD6@scsmsx402.sc.intel.com>
On Wed, Oct 01, 2003 at 11:55:45AM -0700, Nakajima, Jun wrote:
> Just curious. Why do we want to know L1D/L1I cache size?
Entirely cosmetic reasons.
At boot time we print out..
Sep 21 16:38:08 hardwired kernel: CPU: Trace cache: 12K uops, L1 D cache: 8K
Sep 21 16:38:08 hardwired kernel: CPU: L2 cache: 512K
> If you do, then you might want to know the associativity and line size as well.
See http://www.codemonkey.org.uk/projects/x86info
It does all this, and more. Entirely in userspace, where such cosmetics
belong IMO.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-10-01 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 18:55 Dave Jones: Fix cache size of Centrino CPU Nakajima, Jun
2003-10-01 19:27 ` Dave Jones [this message]
[not found] <200310011805.h91I5L88013845@hera.kernel.org>
2003-10-01 18:33 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031001192722.GF25612@redhat.com \
--to=davej@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox