> yes, but still that is a global attribute:
Ok ... I am starting to see where you are going with this.
Well, certainly not global in the sense that a selected cache would be
spread over the whole system. The data set read in by the job in one
cpuset must not pollute the memory of another cpuset.
But it -might- work to mark certain caches to be memory spread across
the current cpuset (to be precise, across current->mems_allowed), as
the default kernel placement policy for those selected caches, with
no per-cpuset mechanism to specify otherwise.
Or it might not work.
I don't know tonight.
I will have to wait for others to chime in.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Andrew Morton <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Andrew Morton <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Paul Jackson <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Andrew Morton <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Paul Jackson <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Paul Jackson <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Paul Jackson <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- From: Ingo Molnar <[email protected]>
- Re: [PATCH 1/5] cpuset memory spread basic implementation
- Prev by Date: Re: [RFC][PATCH 1/5] Virtualization/containers: startup
- Next by Date: Re: [PATCH 1/5] cpuset memory spread basic implementation
- Previous by thread: Re: [PATCH 1/5] cpuset memory spread basic implementation
- Next by thread: Re: [PATCH 1/5] cpuset memory spread basic implementation
- Index(es):
 |