From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: /proc/cpuinfo bad cache info
Date: 7 Sep 2001 11:16:49 -0700 [thread overview]
Message-ID: <9nb2uh$346$1@cesium.transmeta.com> (raw)
In-Reply-To: <3B98DD93.4BDD367C@uni-mb.si>
Followup to: <3B98DD93.4BDD367C@uni-mb.si>
By author: David Balazic <david.balazic@uni-mb.si>
In newsgroup: linux.dev.kernel
>
> In recent 2.4.x kernels the "Cache: " line in /proc/cpuinfo
> reports the amount of the L1 cache or L2 cache or L3 cache or
> some combination of them, depending on what code is executed
> for this ( different for different CPU types ).
>
> Somebody should decide what information should be reported in that
> line and then fix the code.
>
We already DO report the information we care about -- the SMP
weighting value -- and thus the code is correct. The value indicates
how much data is localized to that CPU and therefore how expensive it
is to reschedule a process elsewhere.
Anything that reports anything else is buggy. This includes things
like adding in the L1 cache in an inclusive cache design, or reporting
the L3 cache when it is a shared cache in the chipset.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-09-07 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 14:45 /proc/cpuinfo bad cache info David Balazic
2001-09-07 18:16 ` H. Peter Anvin [this message]
2001-09-07 22:17 ` Alan Cox
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='9nb2uh$346$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox