* Nick Piggin <[email protected]> wrote:
> This is Suresh's patch with some modifications.
> Remove degenerate scheduler domains during the sched-domain init.
actually, i'd suggest to not do this patch. The point of booting with a
CONFIG_NUMA kernel on a non-NUMA box is mostly for testing, and the
'degenerate' toplevel domain exposed conceptual bugs in the
sched-domains code. In that sense removing such 'unnecessary' domains
inhibits debuggability to a certain degree. If we had this patch earlier
we'd not have experienced the wrong decisions taken by the scheduler,
only on the much rarer 'really NUMA' boxes.
is there any case where we'd want to simplify the domain tree? One more
domain level is just one (and very minor) aspect of CONFIG_NUMA - i'd
not want to run a CONFIG_NUMA kernel on a non-NUMA box, even if the
domain tree got optimized. Hm?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
