Re: [Lse-tech] [PATCH] cpusets - big numa cpu and memory placement

[Martin J. Bligh]

>     * Interrupts are not under consideration right now. They land where
>       they land, and this may affect exclusive sets.  If this is a
>       problem, for now, you simply lay out your hardware and exclusive
>       sets more intelligently.

They're easy to fix, just poke the values in /proc appropriately (same
as cpus_allowed, exactly).
 
>     * Memory allocation has a tendency and preference, but no hard policy
>       with regards to where it comes from.  A task which starts on one
>       part of the system but moves to another may have all its memory
>       allocated relatively far away.  In unusual cases, it may acquire
>       remote memory because that's all that's left.  A memory allocation
>       policy similar to cpus_allowed might be needed. (Martin?)

The membind API already does this.

M.
-
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/