From: Jason Lunz <lunz@falooley.org>
To: linux-kernel@vger.kernel.org
Subject: Re: detecting hyperthreading in linux 2.4.19
Date: Thu, 9 Jan 2003 21:57:09 +0000 (UTC) [thread overview]
Message-ID: <slrnb1rs3q.3u8.lunz@stoli.localnet> (raw)
In-Reply-To: <200301091337.04957.jamesclv@us.ibm.com>
jamesclv@us.ibm.com said:
> I don't know of any way to do this in userland. The whole point is
> that the sibling processors are supposed to look like real ones.
That's unfortunately not always true. I'm writing a program that will
run on a system that will be doing high-load routing. Testing has shown
that we get better performance when binding each NIC's interrupts to a
separate physical processor using /proc/irq/*/smp_affinity (especially
when all the interrupts would hit the first CPU, another problem i've
yet to address). That only works for real processors, though, not
HT siblings.
I'm writing a program to run on machines of unknown (by me)
configuration, that will spread out the NIC interrupts appropriately.
So userspace needs to know the difference, at least until interrupts can
be automatically distributed by the kernel in a satisfactory way.
Jason
next prev parent reply other threads:[~2003-01-09 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:02 Jason Lunz
2003-01-09 21:37 ` James Cleverdon
2003-01-09 21:54 ` John Bradford
2003-01-10 0:16 ` James Cleverdon
2003-01-10 0:58 ` Mike Dresser
2003-01-09 21:57 ` Jason Lunz [this message]
2003-01-10 12:29 ` Mark Hounschell
2003-01-10 7:05 ` Mikael Pettersson
2003-01-10 11:05 ` Dave Jones
2003-01-10 11:19 ` Mikael Pettersson
2003-01-10 0:20 ` Dave Jones
2003-01-09 22:29 Kamble, Nitin A
2003-01-09 23:26 Pallipadi, Venkatesh
2003-01-10 8:16 Pallipadi, Venkatesh
2003-01-10 8:43 ` Mikael Pettersson
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=slrnb1rs3q.3u8.lunz@stoli.localnet \
--to=lunz@falooley.org \
--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
all inboxes | Powered by JetHome®