+ MPOL_F_RELATIVE_NODES: This flag specifies that the nodemask passed
+ by the user should remain in the same context as it is for the
+ current task or VMA's set of accessible nodes after the memory
+ policy has been defined.
+
+ Without this flag (and without MPOL_F_STATIC_NODES), anytime a
+ mempolicy is rebound because of a change in the set of
+ accessible nodes, the node (Preferred) or nodemask (Bind,
+ Interleave) is remapped to the new set of accessible nodes.
+ With this flag, the remap is done to ensure the context of the
+ previous nodemask with its set of allowed mems is preserved.
Hmmm ... I've read this several times now ... still can't figure out
what it's saying ;). And it doesn't really explain key aspects of
MPOL_F_RELATIVE_NODES, such as that it provides cpuset relative
numbering (use nodes 0..N-1, regardless of your current cpuset, to
refer to the first N nodes in whatever is your current cpuset.)
Perhaps we'd be further ahead of the game if you started with the
documentation changes to Documentation/vm/numa_memory_policy.txt,
in my patch:
Date: Sun, 23 Dec 2007 22:24:02 -0600
From: Paul Jackson <[EMAIL PROTECTED]>
To: David Rientjes <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [RFC] cpuset relative memory policies - second choice
Message-Id: <[EMAIL PROTECTED]>
Change MPOL_MASK_REL to MPOL_F_RELATIVE_NODES and similar changes.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.940.382.4214
--
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/
