From: Nick Piggin <piggin@cyberone.com.au>
To: linux-kernel <linux-kernel@vger.kernel.org>,
LSE <lse-tech@lists.sourceforge.net>
Subject: General scheduling domains take 2
Date: Wed, 26 Nov 2003 20:17:37 +1100 [thread overview]
Message-ID: <3FC46FB1.2080604@cyberone.com.au> (raw)
Hi,
http://www.kerneltrap.org/~npiggin/w24/
I have progressed a bit further, and the data structure is slightly
changed.
I have done code to build the scheduling description for SMT P4s. It
can be enabled with a new config option although don't try this with
NUMA yet (easy to fix). Note this is quite unlikely to actually do
any good on a pentium 4 because I haven't been able to test it!
The generic scheduling description works nicely on the 16 way NUMAQ
at OSDL and gives results very close to those I was getting before,
so I think I have done a good job at recreating that scheduling policy,
and the scheduling domains doesn't appear to have too much overhead.
The data structure is a bit difficult to understand. I have the start
of a paper here http://www.kerneltrap.org/~npiggin/paper.ps.gz but its
only really worth looking at for the pictures at the end for now.
Questions, comments welcome.
Nick
reply other threads:[~2003-11-26 9:20 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=3FC46FB1.2080604@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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