Re: [Lse-tech] [patch] sched-domain cleanups, sched-2.6.5-rc2-mm2-A3

[Andrew Morton <akpm@osdl.org>]

Erich Focht <efocht@hpce.nec.com> wrote:
>
>  > And finally, HPC
>  > applications are the very ones that should be using CPU
>  > affinities because they are usually tuned quite tightly to the
>  > specific architecture.
> 
>  There are companies mainly selling NUMA machines for HPC (SGI?), so
>  this is not a niche market.

It is niche in terms of number of machines and in terms of affected users. 
And the people who provide these machines have the resources to patch the
scheduler if needs be.

Correct me if I'm wrong, but what we have here is a situation where if we
design the scheduler around the HPC requirement, it will work poorly in a
significant number of other applications.  And we don't see a way of fixing
this without either a /proc/i-am-doing-hpc, or a config option, or
requiring someone to carry an external patch, yes?

If so then all of those seem reasonable options to me.  We should optimise
the scheduler for the common case, and that ain't HPC.

If we agree that architecturally sched-domains _can_ satisfy the HPC
requirement then I think that's good enough for now.  I'd prefer that Ingo
and Nick not have to bust a gut trying to get optimum HPC performance
before the code is even merged up.

Do you agree that sched-domains is architected appropriately?