From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH] [2/3] Add missing migrate_pages manpage Date: Fri, 6 Nov 2009 20:16:13 +0100 Message-ID: <20091106191613.GE819@basil.fritz.box> References: <20091106652.255147301@firstfloor.org> <20091106175212.4368EB1627@basil.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-man-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Christoph Lameter Cc: Andi Kleen , mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-man@vger.kernel.org On Fri, Nov 06, 2009 at 01:01:07PM -0500, Christoph Lameter wrote: > On Fri, 6 Nov 2009, Andi Kleen wrote: > > > +moves all pages of the process > > +.I pid > > +that are in memory nodes > > +.I old_nodes > > +to > > +.I new_nodes. > > +Pages not placed in any node in > > in -> on? Probably. > > > +Use > > +.BR get_mempolicy (2) > > +with the > > +.B MPOL_F_MEMS_ALLOWED > > +flag to obtain the set of nodes that are allowed by > > +.\" FIXME Clarify "current cpuset". Is that the cpuset of the caller > > +.\" or the target? > > +the current cpuset. > > get_mempolicy is restricted to the cpuset of the caller. What target? > > If you are talking about migrate_pages() then the restriction is that the > targets have to be within the callers cpuset. I just copied that from the other manpage (it started as a copy), I haven't really thought about that. -Andi -- ak-VuQAYsv1563Yd54FQh9/CA@public.gmane.org -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html