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

[Paul Jackson]

> Yes I can see it not working well when a dentry is put at the other 
> end of a 256 node altix. That is why just spreading it to nearby
> nodes might be an alternative.

As I've suggested earlier in this thread:
=========================================

I suspect that spreading evenly over the current tasks mems_allowed is
just what is needed.

There is nothing special about big Altix systems here; just use
task->mems_allowed.  For all but tasks using MPOL_BIND, this means
spreading the caching over the nodes in the tasks cpuset.

We don't want to spread over a larger area, because cpusets need to
maintain a fairly aggressive containment.  One jobs big data set must
not pollute the cpuset of another job, except in cases involving kernel
distress.

Let the cpusets define what is "the right size" to spread across.
We do not need additional kernel heuristics or options to decide this.

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