From: Jesper Juhl <jju@dif.dk>
To: linux-kernel@vger.kernel.org
Cc: nagyt@otpbank.hu, Matt_Domsch@Dell.com
Subject: RE: Problem determining number of CPUs
Date: 21 Aug 2002 16:37:14 +0200 [thread overview]
Message-ID: <1029940635.7255.185.camel@jju_lnx.backbone.dif.dk> (raw)
In-Reply-To: <20BF5713E14D5B48AA289F72BD372D6821CBA0@AUSXMPC122.aus.amer.dell.com>
On Wed, 2002-08-21 at 16:20, Matt_Domsch@Dell.com wrote:
> > Linux kernel versions 2.4.18, 2.4.19, 2.4.20pre4 do not determine
> > correctly the number of CPUs on our system. We see 8 CPUs
> > instead of 4,
> > however the system works.
> >
> > Our machine: Dell PowerEdge 6600, 4 Xeon 1400 Mhz, 4GB RAM
>
> Yes, this is expected behavior due to hyperthreaded processors.
> http://lists.us.dell.com/pipermail/linux-poweredge/2002-July/003465.html
>
I'm aware that hyperthreading makes each CPU appear as two. But wouldn't
it be possible to determine this fact and report it to the user to avoid
confusion (not everyone knows about hyperthreading) ?
In the case of 4 HT capable CPU's it could be reported like
8 CPUs (4 physical)
or something like that to indicate that there is nothing wrong and the
kernel is simply taking advantage of hyperthreading.
Just my two euro-cents...
/Jesper Juhl
next prev parent reply other threads:[~2002-08-21 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 14:20 Matt_Domsch
2002-08-21 14:37 ` Jesper Juhl [this message]
2002-08-22 21:12 ` Chris Wedgwood
2002-08-23 7:07 ` Helge Hafting
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=1029940635.7255.185.camel@jju_lnx.backbone.dif.dk \
--to=jju@dif.dk \
--cc=Matt_Domsch@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagyt@otpbank.hu \
/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
all inboxes | Powered by JetHome®