From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Athan <aathan_linux_kernel_1542@cloakmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: CPU numbering & hyperthreading
Date: Tue, 18 Jul 2006 16:46:51 -0400 [thread overview]
Message-ID: <200607181649_MC3-1-C55F-72EE@compuserve.com> (raw)
In-Reply-To: <44BC4200.90308@cloakmail.com>
On Mon, 17 Jul 2006 22:05:52 -0400, Andrew Athan wrote:
>
> I have two highly CPU/memory/network intensive processes with 3-5
> threads each. I am using sched_setaffinity calls to make sure these two
> processes never compete for the same physical CPU. Am I right to assume
> that CPU #0 and #1 vs CPU #2 and #3 are separate physical CPUs on a
> 2-CPU w/ hyperthreading box?
>
> I've spent some time looking, but I did not find documentation on
> exactly how CPUs are numbered in a hyperthreaded box.
There's no fixed numbering.
If you want to know the die/core/thread layout, check out
Documentation/cputopology.txt.
--
Chuck
And did we tell you the name of the game, boy, we call it Riding the Gravy Train.
next reply other threads:[~2006-07-18 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 20:46 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 2:05 Andrew Athan
2006-07-18 19:03 ` Keith Mannthey
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=200607181649_MC3-1-C55F-72EE@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=aathan_linux_kernel_1542@cloakmail.com \
--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
Powered by JetHome