Fix up the error return for nodemask containing nodes disallowed by the process' current cpuset. Disallowed nodes are now silently ignored, as long as the nodemask contains at least one node that is on-line, allowed by the process' cpuset and has memory. Now that we have a cpuset man page, we can refer to cpusets directly in the man page text. Signed-off-by: Lee Schermerhorn <lee.schermerhorn@xxxxxx> man2/set_mempolicy.2 | 15 +++++++++------ 1 files changed, 9 insertions(+), 6 deletions(-) Index: man-pages-3.05/man2/set_mempolicy.2 =================================================================== --- man-pages-3.05.orig/man2/set_mempolicy.2 2008-07-29 16:43:03.000000000 -0400 +++ man-pages-3.05/man2/set_mempolicy.2 2008-07-29 16:46:45.000000000 -0400 @@ -60,7 +60,7 @@ memory mapped files mapped using the .BR mmap (2) call with the .B MAP_PRIVATE -flag and that are only read [loaded] from by the task +flag and that are only read [loaded] from by the process and of memory mapped files mapped using the .BR mmap (2) call with the @@ -104,6 +104,11 @@ is zero, the .I nodemask argument is ignored. +Where a +.I nodemask +is required, it must contain at least one node that is on-line, +allowed by the process' current cpuset context, +and contains memory. The .B MPOL_DEFAULT @@ -209,13 +214,11 @@ specifies more than a page worth of bits Or, .I nodemask specifies one or more node IDs that are -greater than the maximum supported node ID, -or are not allowed in the calling task's context. -.\" "calling task's context" refers to cpusets. -.\" No man page avail to ref. --Lee Schermerhorn +greater than the maximum supported node ID. Or, none of the node IDs specified by .I nodemask -are on-line, or none of the specified nodes contain memory. +are on-line and allowed by the process' current cpuset context, +or none of the specified nodes contain memory. .TP .B ENOMEM Insufficient kernel memory was available. -- 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
