* Ingo Molnar <[EMAIL PROTECTED]> wrote:
> > a numa scheduler domain at the top level and cache_hot_time will be
> > set to 0 in that case on smp box. Though this will be a mutt point
> > with recent patch from Suresh Siddha for removing the extra bogus
> > scheduler domains.
> > http://marc.theaimsgroup.com/?t=111240208000001&r=1&w=2
>
> at first sight the dummy domain should not be a problem, [...]
at second sight, maybe it could be a problem after all. It's safe is
load_balance(), where task_hot() should never happen to be called for
the dummy domain. (because the dummy domain has only one CPU group on
such boxes)
But if the dummy domain has SD_WAKE_AFFINE set then it's being
considered for passive migration, and a value of 0 means 'can always
migrate', and in situations where other domains signalled 'task is too
hot', this domain may still override the decision (incorrectly). So the
safe value for dummy domains would a cacheflush time of 'infinity' - to
make sure migration decisions are only done via other domains.
I've changed this in my tree - migration_cost[] is now initialized to
-1LL, which should solve this problem.
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/
