From: Dave Jones <davej@redhat.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cache line size
Date: Sun, 10 Sep 2006 22:39:50 -0400 [thread overview]
Message-ID: <20060911023950.GF4743@redhat.com> (raw)
In-Reply-To: <4504AF26.9040807@comcast.net>
On Sun, Sep 10, 2006 at 08:34:46PM -0400, John Richard Moser wrote:
> Is there a way for the Linux Kernel to know the cache line size of the
> CPU it's on, besides #define X86_CACHE_LINE_SZ 32 or whatnot? I am
> looking in /proc/cpuinfo trying to determine how to run caching
> optimizations and interested in this information and its implications.
> It may also be useful if I can get this information at run time in
> application code.
You can use /dev/cpu/x/cpuid to read it directly from the CPU.
See the source of x86info for examples.
Dave
next prev parent reply other threads:[~2006-09-11 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 0:34 Cache line size John Richard Moser
2006-09-11 2:39 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-11 4:58 Chuck Ebbert
2006-09-11 5:31 ` Dave Jones
2006-09-11 12:41 Chuck Ebbert
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=20060911023950.GF4743@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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