From: Pavel Machek <pavel@suse.cz>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: Jesper Juhl <jju@dif.dk>, linux-kernel@vger.kernel.org
Subject: Re: Problem determining number of CPUs
Date: Tue, 27 Aug 2002 14:47:51 +0000 [thread overview]
Message-ID: <20020827144751.J35@toy.ucw.cz> (raw)
In-Reply-To: <3D65DF4D.68EEA449@aitel.hist.no>; from helgehaf@aitel.hist.no on Fri, Aug 23, 2002 at 09:07:57AM +0200
Hi!
> > In the case of 4 HT capable CPU's it could be reported like
> >
> > 8 CPUs (4 physical)
> >
> Or 8 CPUs (4 chips)
> 2 cpus on a chip may be counterintuitive to some, but there
> isn't anything special about it. They aren't really
> less "physical".
But p4 is not 2cpus on a chip. Its one cpu two register sets.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-08-27 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 14:20 Problem determining number of CPUs Matt_Domsch
2002-08-21 14:37 ` Jesper Juhl
2002-08-22 21:12 ` Chris Wedgwood
2002-08-23 7:07 ` Helge Hafting
2002-08-27 14:47 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-21 14:19 Nagy Tibor
2002-08-21 14:28 ` Richard B. Johnson
2002-08-21 21:06 ` Kelsey Hudson
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=20020827144751.J35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=helgehaf@aitel.hist.no \
--cc=jju@dif.dk \
--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