> I really want cpuset relative nodemasks. Nodes need to reference
> to available nodes. If you set all of them then it will use all available
> nodes and ignore the ones not allowed. If you just set the first two bits
> then it will use the first and second node of a cpuset.
Exactly. I think I am ending up with exactly this.
I'm just getting there by a strange way of thinking
(as usual ;).
--
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:
- [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: Christoph Lameter <[email protected]>
- [patch 1/3] cpusets: extract mmarray loading from update_nodemask
- Prev by Date: Re: [patch 2/2] cpusets: add interleave_over_allowed option
- Next by Date: Re: [RFC 0/3] Recursive reclaim (on __PF_MEMALLOC)
- 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):
 |