public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] When L3 is present show its size in /proc/cpuinfo
Date: Mon, 26 Sep 2005 18:30:37 -0400	[thread overview]
Message-ID: <20050926223037.GN19275@redhat.com> (raw)
In-Reply-To: <20050926145956.B15625@unix-os.sc.intel.com>

On Mon, Sep 26, 2005 at 02:59:56PM -0700, Venkatesh Pallipadi wrote:
 
 > The code that prints the cache size assumes that L3 always lives in chipset and
 > is shared across CPUs. Which is not really true.
 > 
 > I think all the cachesizes reported by cpuid are in the processor itself.
 > The attached patch changes the code to reflect that.
 > 
 > Dave, any idea where that original comment in the code came from?

Been there for a long time iirc (Though I've not checked [my kingdom for
a 'git annotate' tool])

 > Are there any
 > systems which reports the L3 cache size in cpuid, when L3 sits in northbridge?

Very unlikely.
The only legacy system with L3 that I recall was the AMD K6-III (which had on-CPU L1/L2,
though some motherboards at the time also included an L3 (or L2 if used with an earlier
socket 7 cpu).  None of those off-cpu caches were detectable with cpuid, and
required reading from pci config space to determine their size/status etc.

The big question I have though is how relevant that 'weighting' is today
if we factor in L3.

		Dave


      reply	other threads:[~2005-09-26 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-26 21:59 [PATCH] When L3 is present show its size in /proc/cpuinfo Venkatesh Pallipadi
2005-09-26 22:30 ` 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=20050926223037.GN19275@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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