All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Nico Schottelius <nico-kernel@schottelius.org>,
	linux-kernel@vger.kernel.org
Subject: Re: /proc/cpuinfo format - arch dependent!
Date: Mon, 09 May 2005 14:00:55 -0400	[thread overview]
Message-ID: <427FA557.3030400@tmr.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0505062324550.1894-100000@sweetums.bluetronic.net>

Ricky Beam wrote:
> On Tue, 19 Apr 2005, Nico Schottelius wrote:
> 
>>When I wrote schwanz3(*) for fun, I noticed /proc/cpuinfo
>>varies very much on different architectures.
> 
> 
> Yep, and it has been this way since the begining of time.
> 
> 
>>So that one at least can count the cpus on every system the same way.
> 
> 
> Hah.  Give me a minute to stop laughing...  I argued the same point almost
> a decade ago.  Linus decided to be an ass and flat refused to ever export
> numcpu (or any of the current day derivatives) which brought us to the
> bullshit of parsing the arch dependant /proc/cpuinfo.

Don't ever take up a career as a diplomat, no one in their right mind 
would want such a tactless person for a diplomatic job, say UN ambasador 
for instance.

Linus did what was probably right then. I would agree that there is room 
for something better now. Just to prove it could be done (not that this 
is the only or best way):

   cpu0 {
     socket: 0
     chip-cache: 0
     num-core: 2
     per-core-cache: 512k
     num-siblings: 2
     sibling-cache: 0
     family: i86
     features: sse2 sse3 xxs bvd
     # stepping and revision info
   }
   cpu1 {
     socket: 1
     chip-cache: 0
     num-core: 1
     pre-core-cache: 512k
     num-siblings: 2
     sibling-cache: 64k
     family: i86
     features: sse2 sse3 xxs bvd kook2
     # stepping and revision info
   }

This is just proof of concept, you can have per-chip, per-core, and 
per-sibling cache for instance, but I can't believe that anyone would 
make a chip where the cache per core or per sibling differed, or the 
instruction set, etc. Depending on where you buy your BS, Intel and AMD 
will (or won't) make single and dual core chips to fit the same socket.

The complexity wasn't needed a decade ago, and I'm not sure it is now, 
other than it being easy to display if people don't complain about 
breaking the existing format.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  parent reply	other threads:[~2005-05-09 19:25 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 12:15 /proc/cpuinfo format - arch dependent! Nico Schottelius
2005-04-19 13:24 ` Lennart Sorensen
2005-04-19 19:17   ` Lee Revell
2005-04-19 20:00     ` Nico Schottelius
2005-04-19 20:02       ` David S. Miller
2005-04-19 20:12       ` Lennart Sorensen
2005-04-19 20:42       ` Lee Revell
2005-04-19 20:54         ` Nico Schottelius
2005-04-19 21:12           ` Grzegorz Kulewski
2005-04-20 20:31   ` Ralf Baechle
2005-05-07  3:37 ` Ricky Beam
2005-05-07  4:01   ` Stefan Smietanowski
2005-05-07  7:55     ` Ricky Beam
2005-05-07 17:51       ` Stefan Smietanowski
2005-05-07 18:05         ` Ricky Beam
2005-05-07 18:46           ` Dr. David Alan Gilbert
2005-05-07  4:14   ` Andrew Morton
2005-05-07  7:58     ` Willy Tarreau
2005-05-07 16:53       ` Dave Jones
2005-05-07 17:05         ` Willy Tarreau
2005-05-07 17:20           ` Dave Jones
2005-05-07 17:18             ` Willy Tarreau
2005-05-08  1:25             ` Jim Nance
2005-05-08 16:11               ` John Kacur
2005-05-09 18:14               ` Bill Davidsen
2005-05-09 20:09                 ` Chris Friesen
2005-05-09 20:26                   ` Lennart Sorensen
2005-05-09 21:25                     ` Brian O'Mahoney
2005-05-10 16:21                   ` Bill Davidsen
2005-05-10 16:34                     ` Chris Friesen
2005-05-10  2:23                 ` Jim Nance
2005-05-10  4:12                   ` Willy Tarreau
2005-05-10  7:13                   ` Paul Jackson
2005-05-10 16:34                   ` Bill Davidsen
2005-05-07 17:54       ` Stefan Smietanowski
2005-05-07 18:05         ` Willy Tarreau
2005-05-09 18:03     ` Bill Davidsen
2005-05-10  7:21     ` Paul Jackson
2005-05-10 14:38       ` Lennart Sorensen
2005-05-10 16:37         ` Bill Davidsen
2005-05-09 18:00   ` Bill Davidsen [this message]
2005-05-09 19:58     ` Lennart Sorensen
2005-05-10 16:49       ` Bill Davidsen
     [not found] <3UZS7-5ue-17@gated-at.bofh.it>
     [not found] ` <41ouh-4QE-1@gated-at.bofh.it>
     [not found]   ` <41oXl-5hl-7@gated-at.bofh.it>
     [not found]     ` <41sxX-8cN-11@gated-at.bofh.it>
     [not found]       ` <41BL4-7l7-15@gated-at.bofh.it>
2005-05-07 23:33         ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-05-08 13:24           ` Andi Kleen

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=427FA557.3030400@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel@schottelius.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.