From: Robert Love <rml@tech9.net>
To: Scott Robert Ladd <scott@coyotegulch.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /proc/cpuinfo and hyperthreading
Date: 15 Dec 2002 23:02:39 -0500 [thread overview]
Message-ID: <1040011359.3458.556.camel@phantasy> (raw)
In-Reply-To: <FKEAJLBKJCGBDJJIPJLJCEJPDLAA.scott@coyotegulch.com>
On Sun, 2002-12-15 at 22:58, Scott Robert Ladd wrote:
> Am I correct to infer that the "siblings" entry refers to the 2-way
> hyperthreading on my CPU?
Yep, the 'siblings' value is the number of virtual processors in the
physical package.
Do you only see one processor listing in /proc/cpuinfo, though? You
should see one for each (virtual) processor. That means two in a single
HT-enabled P4, each with the same physical id.
So it seems your chip works... is the kernel compiled for SMP?
Robert Love
next prev parent reply other threads:[~2002-12-16 3:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200212160004.gBG04g130091@hera.kernel.org>
2002-12-16 2:34 ` [XFS] add missing file xfs_iomap.c Anders Gustafsson
2002-12-16 3:58 ` /proc/cpuinfo and hyperthreading Scott Robert Ladd
2002-12-16 4:02 ` Robert Love [this message]
2002-12-16 4:13 ` Scott Robert Ladd
2002-12-16 6:28 ` Zwane Mwaikambo
2002-12-16 6:35 ` Zwane Mwaikambo
2002-12-16 13:38 ` Scott Robert Ladd
2002-12-16 13:54 ` Brian Jackson
2002-12-16 14:10 ` Richard B. Johnson
2002-12-16 14:56 ` Scott Robert Ladd
2002-12-16 15:11 ` Måns Rullgård
2002-12-16 15:44 ` HT Benchmarks (was: /proc/cpuinfo and hyperthreading) Scott Robert Ladd
2002-12-16 22:38 ` J.A. Magallon
2002-12-16 23:21 ` Scott Robert Ladd
2002-12-16 23:27 ` J.A. Magallon
2002-12-17 11:03 ` Denis Vlasenko
2002-12-17 20:44 ` H. Peter Anvin
2002-12-16 23:50 ` H. Peter Anvin
2002-12-17 19:27 ` Bill Davidsen
2002-12-16 15:52 ` /proc/cpuinfo and hyperthreading Andrew Theurer
2002-12-16 14:08 ` Dave Jones
2002-12-16 14:36 ` Scott Robert Ladd
2002-12-16 4:39 ` [XFS] add missing file xfs_iomap.c Linus Torvalds
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=1040011359.3458.556.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@coyotegulch.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.