All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Why /proc/cpuinfo doesn't print L1,L2,L3 caches?
Date: Tue, 25 Mar 2008 21:39:13 -0400	[thread overview]
Message-ID: <20080326013913.GC6384@codemonkey.org.uk> (raw)
In-Reply-To: <998d0e4a0803251439u4bf09fb1ye568fc1970b0200f@mail.gmail.com>

On Tue, Mar 25, 2008 at 10:39:39PM +0100, J.C. Pizarro wrote:
 
 > How can i know what hw-caches use the processors?
 > The current kernel doesn't know well what hw-caches uses.
 > 
 > The good proposal is by example (the data below are not real):
 > * In old AMD Athlon64:
 > 
 > cache L1        : 64 KiB I + 64 KiB D, 64 B line, direct way, ...
 > cache L2        : 512 KiB I+D-shared, exclusive, 128 associative way, ...
 > cache L3        : none
 > 
 > * In Intel Core Duo:
 > processor       : 0
 > cache L1        : 32 KiB I + 32 KiB D, 64 B line, direct way, ...
 > cache L2        : 2048 KiB Cores-shared, inclusive, 128 associative way, ...
 > cache L3        : none
 > 
 > processor       : 1
 > cache L1        : 32 KiB I + 32 KiB D, 64 B line, direct way, ...
 > cache L2        : 2048 KiB cores-shared, inclusive, 128 associative way, ...
 > cache L3        : none
 > 
 > * In Quad:
 > processor       : 0
 > cache L1        : 32 KiB I + 32 KiB D, 64 B line, direct way, ...
 > cache L2        : 2048+2048 KiB pair-cores-shared, inclusive, 128
 > associative way, ...
 > cache L3        : none
 > ...
 > processor       : 3
 > cache L1        : 32 KiB I + 32 KiB D, 64 B line, direct way, ...
 > cache L2        : 2048+2048 KiB pair-cores-shared, inclusive, 128
 > associative way, ...
 > cache L3        : none

See x86info.  http://www.codemonkey.org.uk/projects/x86info/

	Dave

-- 
http://www.codemonkey.org.uk

      parent reply	other threads:[~2008-03-26  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25 21:39 Why /proc/cpuinfo doesn't print L1,L2,L3 caches? J.C. Pizarro
2008-03-25 21:57 ` Chris Snook
2008-03-25 22:50   ` J.C. Pizarro
2008-03-25 22:59     ` Chris Snook
2008-03-25 23:10       ` J.C. Pizarro
2008-03-25 23:14         ` Chris Snook
2008-03-26  4:29   ` Andrey Borzenkov
2008-03-26  8:54   ` consistency: temperature versus metric bytes (was: Re: Why /proc/cpuinfo doesn't print L1,L2,L3 caches?) Geert Uytterhoeven
2008-03-26  1:39 ` Dave Jones [this message]

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=20080326013913.GC6384@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=jcpiza@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.