public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Jesper Juhl <jju@dif.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem determining number of CPUs
Date: Fri, 23 Aug 2002 09:07:57 +0200	[thread overview]
Message-ID: <3D65DF4D.68EEA449@aitel.hist.no> (raw)
In-Reply-To: 1029940635.7255.185.camel@jju_lnx.backbone.dif.dk

Jesper Juhl wrote:

> 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".

Helge Hafting

  parent reply	other threads:[~2002-08-23  7:01 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 [this message]
2002-08-27 14:47     ` Pavel Machek
  -- 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=3D65DF4D.68EEA449@aitel.hist.no \
    --to=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