All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Stefan Smietanowski <stesmi@stesmi.com>,
	Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: /proc/cpuinfo format - arch dependent!
Date: Sat, 7 May 2005 19:46:10 +0100	[thread overview]
Message-ID: <20050507184610.GE7130@gallifrey> (raw)
In-Reply-To: <Pine.GSO.4.33.0505071351360.19035-100000@sweetums.bluetronic.net>

* Ricky Beam (jfbeam@bluetronic.net) wrote:
> 
> Your HT DC CPU counts as 4 cpus total... the same as two HT processors.
> The system does not fundamentally need to make a distinction on dual core
> vs. two actual chips + heat sinks + fans.  The system will perform almost
> identically (if not acutally identically) to a dual (single core) processor
> system.

That *might* be the case for a current one; but I'm sure dual core
processors will end up sharing a level of cache/bus arbitration
sometime.  Anyway it is a bit nasty not to real dual-core'd ness
to things, after all they might get upset if someone tried to hotswap
one.....

Dave
P.S. On the side note of early dual core chips; there is an R65c00/21
and R65c29 listed in a 1985 Rockwell datasheet I've got - dual 6502s!

 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  reply	other threads:[~2005-05-07 18:46 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 [this message]
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
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=20050507184610.GE7130@gallifrey \
    --to=gilbertd@treblig.org \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stesmi@stesmi.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 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.