Re: [PATCH 01/02] cpuset memory spread slab cache filesys

[Paul Jackson]

Andi wrote:
> The main reason i'm reluctant to use this is that the cpuset fast path
> overhead (e.g. in memory allocators etc.) is quite large

I disagree.

I spent much time minimizing that overhead over the last few months, as
a direct result of your recommendation to do so.

Especially in the case that all tasks are in the root cpuset (as in the
scenario I just suggested for setting this memory spreading policy for
all tasks), the overhead is practically zero.  The key hook is an
inline test done (usually) once per page allocation on an essentially
read only global 'number_of_cpusets' that determines it is <= 1.

I disagree with your "quite large" characterization.

Please explain further.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@xxxxxxx> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/