From: Nathan Fredrickson <8nrf@qlink.queensu.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: hyperthreading-aware scheduler
Date: 23 Jul 2003 17:07:23 -0400 [thread overview]
Message-ID: <1058994421.3186.89.camel@rocky> (raw)
On Fri, Jul 11, 2003, Andrew Theurer wrote:
> On Friday 11 July 2003 14:59, Mike Fedyk wrote:
> > On Fri, Jul 11, 2003 at 02:37:12PM -0500, Andrew Theurer wrote:
> > > On Friday 11 July 2003 09:02, Dave Jones wrote:
> > > > Process scheduler improvements.
> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > > > - Scheduler is now Hyperthreading SMP aware and will disperse processes
> > > > over physically different CPUs, instead of just over logical CPUs.
> > >
> > > I'm pretty sure this is not in 2.5 (unless it's in bk after 2.5.75)
> >
> > wasn't this merged back in 2.4.6x?
>
> I believe that was support of, not enhancement for HT. Actually there may
> have been some enhancements in other areas, but not scheduler.
Now that we have support of HT, what is the status hyperthreading-aware
scheduler? Do any of the testing-trees have a hyperthreading-aware
scheduler?
Ingo has some HT-scheduler patches here:
http://people.redhat.com/mingo/O(1)-scheduler/
The most recent is for 2.5.68, but unfortunately due to other problems I
have only been able to run kernels 2.5.70 and greater. Also my attempts
at forward-porting Ingo's 2.5.68 patch have not been successful.
I have access to dual and quad HT-enabled systems and would be happy to
do some testing as I learn more about the scheduler. SMP w/ HT systems
have scheduling issues that don't exist in a UP w/ HT system. For
example when there are 4 compute intensive threads in quad HT system
they should be scheduled on physically unique processors. This does not
happen with the current scheduler even in an otherwise completely idle
system. Two threads often end up on the same physical processor and
remain there due to their affinity.
Nathan
reply other threads:[~2003-07-23 20:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1058994421.3186.89.camel@rocky \
--to=8nrf@qlink.queensu.ca \
--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;
as well as URLs for NNTP newsgroup(s).