Another attempt to rationalize description of MPOL_DEFAULT.
Since ~2.6.25, the system default memory policy is "local allocation".
MPOL_DEFAULT itself is a request to remove any non-default policy and
"fall back" to the surrounding context. Try to say that without delving
into implementation details.
CONFORMING TO: According to POSIX.1, the behavior of getcwd()
is unspecified for the buf==NULL case.
Add an introductory paragraph giving an overview of what these functions do.
Fix error in description of getwd(): it does not truncate the
pathname; rather, it gives an error if the pathname exceeds PATH_MAX bytes.
Rewrote RETURN VALUE section.
Add EINVAL ENAMETOOLONG errors for getwd().
Various other clarifications and wording fixes.
CONFORMING TO: POSIX.1-2001 does not define any errors for getwd().
Update the get_mempolicy(2) man page to add in the description of
the MPOL_F_MEMS_ALLOWED flag, added in 2.6.23.
mtk
Document additional EINVAL error that occurs is MPOL_F_MEMS_ALLOWED
is specified with either MPOL_F_ADDR or MPOL_F_NODE.
Misc cleanup of get_mempolicy(2):
+ mention that any mode flags will be saved with mode.
I don't bother to document mode flags here because we
already have a pointer to set_mempolicy(2) for more info
on memory policy. mode flags are discussed there.
+ remove some old, obsolete [IMO] NOTES and 'roff comments.
PF_ constants have always had the same values; there never has
been a protocol family that had more than one address family,
and POSIX.1-2001 only specifies the AF_* constants.
PF_ constants have always had the same values; there never has
been a protocol family that had more than one address family,
and POSIX.1-2001 only specifies the AF_* constants.
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.
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.