On Thu, 2007-10-25 at 20:58 -0700, David Rientjes wrote: > On Thu, 25 Oct 2007, Paul Jackson wrote: > > > The user space man pages for set_mempolicy(2) are now even more > > behind the curve, by not mentioning that MPOL_INTERLEAVE's mask > > might mean nothing, if (1) in a cpuset marked memory_spread_user, > > (2) after the cpuset has changed 'mems'. > > > > Yeah. They were already outdated in the sense that they did not specify > that the interleave nodemask could change as a result of a cpuset mems > change. > > > I wonder if there is any way to fix that. Who does the man pages > > for Linux system calls? > >
Michael Kerrisk, whom I've copied, does. I recently sent in an update to all of the mempolicy man pages that describe the behavior as it currently exists. [I need to send in an update for MPOL_F_MEMS_ALLOWED]. One of the things that has bothered me is that there are no cpuset man pages to reference from the mempolicy man pages. [I know, we can and do refer to the kernel source Documentation, but that might not be available to everyone w/o some digging. "See Also" refs typically point at other man pages...]. To get around this, I had to talk about "nodes allowed in the current context" or some such weasel-wording in my updates. Paul: what do you think about subsetting the cpuset.txt into a man page or 2 that can be referenced by other man pages' See Also sections? > <snip> > > David Lee - 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/
