On Fri, 04 Apr 2008 11:00:40 -0400 Lee Schermerhorn wrote: > PATCH 09/15 Mempolicy: Use MPOL_PREFERRED for system-wide default policy > > Against: 2.6.25-rc8-mm1 > > Signed-off-by: Lee Schermerhorn <lee.schermerhorn@xxxxxx> > > Documentation/vm/numa_memory_policy.txt | 52 ++++++++---------------- > mm/mempolicy.c | 68 +++++++++++++++++++------------- > 2 files changed, 59 insertions(+), 61 deletions(-) > > Index: linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt > =================================================================== > --- linux-2.6.25-rc8-mm1.orig/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:26.000000000 -0400 > +++ linux-2.6.25-rc8-mm1/Documentation/vm/numa_memory_policy.txt 2008-04-02 17:47:37.000000000 -0400 > @@ -187,19 +170,18 @@ Components of Memory Policies > > MPOL_PREFERRED: This mode specifies that the allocation should be > attempted from the single node specified in the policy. If that > - allocation fails, the kernel will search other nodes, exactly as > - it would for a local allocation that started at the preferred node > - in increasing distance from the preferred node. "Local" allocation > - policy can be viewed as a Preferred policy that starts at the node > + allocation fails, the kernel will search other nodes, in order of > + increasing distance from the preferred node based on information > + provided by the platform firmware. > containing the cpu where the allocation takes place. Something in the patch lines above seems to be foobarred. I.e., the sentences/lines don't flow correctly. > Internally, the Preferred policy uses a single node--the --- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-numa" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
