Attempt to claify discussion of MPOL_DEFAULT. Signed-off-by: Lee Schermerhorn <lee.schermerhorn@xxxxxx> man2/mbind.2 | 18 +++++++++++++----- 1 files changed, 13 insertions(+), 5 deletions(-) Index: man-pages-3.05/man2/mbind.2 =================================================================== --- man-pages-3.05.orig/man2/mbind.2 2008-07-29 16:53:48.000000000 -0400 +++ man-pages-3.05/man2/mbind.2 2008-07-29 16:54:13.000000000 -0400 @@ -184,7 +184,8 @@ the memory policy reverts to The .B MPOL_DEFAULT -mode specifies that the default policy should be used. +mode requests that any non-default policy be removed, +restoring default behavior. When applied to a range of memory via .BR mbind (), this means to use the process policy, @@ -193,7 +194,7 @@ which may have been set with If the mode of the process policy is also .BR MPOL_DEFAULT , the system-wide default policy will be used. -The system-wide default policy will allocate +The system-wide default policy allocates pages on the node of the CPU that triggers the allocation. For .BR MPOL_DEFAULT , @@ -399,20 +400,27 @@ is ignored on huge page mappings. The .BR MPOL_DEFAULT , -mode has different effects for +mode can have different effects for .BR mbind () and .BR set_mempolicy (2). When .B MPOL_DEFAULT +is specified for +.BR set_mempolicy (2), +the process' policy reverts to system default policy +or local allocation. +When +.B MPOL_DEFAULT is specified for a range of memory using .BR mbind (), any pages subsequently allocated for that range will use the process's policy, as set by .BR set_mempolicy (2). This effectively removes the explicit policy from the -specified range. -To select "local allocation" for a memory range, +specified range, "falling back" to a possibly non-default +policy. +To select explicit "local allocation" for a memory range, specify a .I mode of -- 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
