|| ||Nick Piggin <firstname.lastname@example.org>|
|| ||linux-kernel <email@example.com>,
|| ||General scheduling domains take 2|
|| ||Wed, 26 Nov 2003 20:17:37 +1100|
I have progressed a bit further, and the data structure is slightly
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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/