From: "Martin.Knoblauch" <Martin.Knoblauch@TeraPort.de>
To: Dave Jones <davej@suse.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo
Date: Wed, 23 May 2001 11:24:22 +0200 [thread overview]
Message-ID: <3B0B81C6.14770A10@TeraPort.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0105230307470.4030-100000@Appserv.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Dave Jones wrote:
>
> On Wed, 23 May 2001, Tomas Telensky wrote:
>
> > Yes. Recently I tried to transform whole cpuid code to a userspace
> > utility. Not easy, not clean... but it worked.
>
> See http://www.sourceforge.net/projects/x86info
> or ftp://ftp.suse.com/pub/people/davej/x86info/
>
thanks for the pointer. Definitely gives some very interesting
information about ones x86 CPU. At least something to work on. The
output for different CPU types is a bit incoherent, making it difficult
to parse. That why I [still] think (yes I'm stubborn :-) that having the
cache sizes in /proc/cpuinfo in one format is a good idea. The info is
there, it is just the output. With the userland tool, you always may
have discrepancies between the kernels view and the tools view.
But I agree, it does not *have* to go into the kernel.
Cheers
MArtin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Card for Martin.Knoblauch --]
[-- Type: text/x-vcard; charset=us-ascii; name="Martin.Knoblauch.vcf", Size: 375 bytes --]
begin:vcard
n:Knoblauch;Martin
tel;cell:+49-170-4904759
tel;fax:+49-89-510857-111
tel;work:+49-89-510857-309
x-mozilla-html:FALSE
url:http://www.teraport.de
org:TeraPort GmbH;C+ITS
adr:;;Garmischer Straße 4;München;Bayern;D-80339;Germany
version:2.1
email;internet:Martin.Knoblauch@TeraPort.de
title:Senior System Engineer
x-mozilla-cpt:;-7008
fn:Martin Knoblauch
end:vcard
next prev parent reply other threads:[~2001-05-23 9:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 8:52 [Patch] Output of L1,L2 and L3 cache sizes to /proc/cpuinfo Martin.Knoblauch
2001-05-22 9:55 ` Martin.Knoblauch
2001-05-22 16:55 ` H. Peter Anvin
2001-05-22 18:08 ` Alan Cox
2001-05-22 23:57 ` Martin Knoblauch
2001-05-23 0:05 ` H. Peter Anvin
2001-05-23 0:18 ` Tomas Telensky
2001-05-23 1:08 ` Dave Jones
2001-05-23 9:24 ` Martin.Knoblauch [this message]
2001-05-23 1:48 ` Dave Jones
2001-05-23 7:10 ` Martin.Knoblauch
2001-05-22 16:52 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 12:39 Martin.Knoblauch
2001-05-21 15:16 ` H. Peter Anvin
2001-05-22 2:59 ` Steven Walter
2001-05-22 3:22 ` Dave Jones
2001-05-22 4:44 ` David Weinehall
2001-05-22 11:15 ` Dave Jones
2001-05-22 22:47 ` Tomas Telensky
2001-05-22 23:43 ` Dave Jones
2001-05-22 23:50 ` Martin Knoblauch
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=3B0B81C6.14770A10@TeraPort.de \
--to=martin.knoblauch@teraport.de \
--cc=davej@suse.de \
--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