From: David Balazic <david.balazic@uni-mb.si>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: /proc/cpuinfo bad cache info
Date: Fri, 07 Sep 2001 16:45:39 +0200 [thread overview]
Message-ID: <3B98DD93.4BDD367C@uni-mb.si> (raw)
Hi!
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.
Party on !
--
David Balazic
--------------
"Be excellent to each other." - Bill S. Preston, Esq., & "Ted" Theodore Logan
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2001-09-07 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 14:45 David Balazic [this message]
2001-09-07 18:16 ` /proc/cpuinfo bad cache info H. Peter Anvin
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=3B98DD93.4BDD367C@uni-mb.si \
--to=david.balazic@uni-mb.si \
--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