Re: [PATCH 1/5] cpuset memory spread basic implementation

Ingo wrote:
the case Paul's patch is addressing: workloads which are
known to be global (and hence spreading out is the best-performing
allocation).

Just to be clear, note that even in my case, we require the node-local
policy for some allocations (into the users portion of the address
space) at the same time we require the spread policy (not
sure I like 'global' here) for other allocations (file stuff).

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