Lee,
Lee Schermerhorn wrote:
Fix error conditions, now that the kernel silently ignores
nodes outside the task's cpuset, as long as one valid node
remains.
Now that cpuset man page exists, we can refer to it. Remove
stale comment regarding lack thereof.
Thanks. Applied for man-pages-3.07.
Cheers,
Michael
Signed-off-by: Lee Schermerhorn <lee.schermerhorn@xxxxxx>
man2/mbind.2 | 15 +++++++++------
1 files changed, 9 insertions(+), 6 deletions(-)
Index: man-pages-3.05/man2/mbind.2
===================================================================
--- man-pages-3.05.orig/man2/mbind.2 2008-07-29 16:40:28.000000000 -0400
+++ man-pages-3.05/man2/mbind.2 2008-07-29 16:52:10.000000000 -0400
@@ -139,6 +139,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
@@ -303,19 +308,17 @@ and
is empty.
Or,
.I maxnode
-exceeds kernel-imposed limit.
+exceeds a kernel-imposed limit.
.\" As at 2.6.23, this limit is "a page worth of bits", e.g.,
.\" 8 * 4096 bits, assuming a 4kB page size.
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 EIO
.B MPOL_MF_STRICT
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
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
