> Will it handle the case of MPOL_INTERLEAVE policy on a shm segment that
> is mapped by tasks in different, possibly disjoint, cpusets. Local
> allocation does, and my patch does. That was one of the primary
> goals--to address an issue that Christoph has with shared policies.
> cpusets really muck these up!
It probably won't handle that. I don't get along too well with shmem.
Can you to an anti-shmem bigot how MPOL_INTERLEAVE should work with
shmem segments mapped in diverse ways by different tasks in different
cpusets? What would be the key attribute(s) of a proper solution?
Maybe if we keep it simple enough, I can avoid mucking it up too much
this time around.
--
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/
- Follow-Ups:
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Lee Schermerhorn <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Christoph Lameter <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- References:
- [patch 1/3] cpusets: extract mmarray loading from update_nodemask
- From: David Rientjes <[email protected]>
- [patch 2/3] mempolicy: mpol_rebind_policy cleanup
- From: David Rientjes <[email protected]>
- [patch 3/3] cpusets: add memory_spread_user option
- From: David Rientjes <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Paul Jackson <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: David Rientjes <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Paul Jackson <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Paul Jackson <[email protected]>
- Re: [patch 3/3] cpusets: add memory_spread_user option
- From: Lee Schermerhorn <[email protected]>
- [patch 1/3] cpusets: extract mmarray loading from update_nodemask
- Prev by Date: Re: [PATCH] Intel FB pixel clock calculation fix
- Next by Date: Re: Is gcc thread-unsafe?
- Previous by thread: Re: [patch 3/3] cpusets: add memory_spread_user option
- Next by thread: Re: [patch 3/3] cpusets: add memory_spread_user option
- Index(es):
 |