David wrote:
> Of course they have specific affinity needs, that's why they used
> mempolicies.
No. Good grief. If they are just looking for some set of memory
banks, not to other node-specific hardware, then they might not need
a specific node.
Consider for example a multi-threaded, compute bound, long running
scientific computation that has a substantial and fussy memory layout.
Remapping it from one cpuset to another having the same NUMA topology
may well work fine, once its memory caches recover. Reverting it to
the lowest common denominator MPOL_DEFAULT policy because (Choice C) it
no longer has access to its initial nodes might devastate its
performance.
pj wrote:
> I sure wish I knew what real world, actual, not hypothetical, situations
> were motivating this.
I'm still wishing ...
--
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/2] cpusets: extract mmarray loading from update_nodemask
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Lee Schermerhorn <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Christoph Lameter <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: Paul Jackson <[email protected]>
- Re: [patch 2/2] cpusets: add interleave_over_allowed option
- From: David Rientjes <[email protected]>
- [patch 1/2] cpusets: extract mmarray loading from update_nodemask
- Prev by Date: Re: Licensing of IS89C35 WLAN USB driver [was Re: rt73usb: support for wireless in Kohjinsha subnotebook]
- Next by Date: Re: [PATCH] dump_stack on panic
- Previous by thread: Re: [patch 2/2] cpusets: add interleave_over_allowed option
- Next by thread: Re: [patch 2/2] cpusets: add interleave_over_allowed option
- Index(es):
 |