From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Jackson Date: Fri, 15 Jul 2005 06:05:01 +0000 Subject: Re: [NUMA] Display and modify the memory policy of a process Message-Id: <20050714230501.4a9df11e.pj@sgi.com> List-Id: References: <200507150452.j6F4q9g10274@unix-os.sc.intel.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christoph Lameter Cc: kenneth.w.chen@intel.com, linux-mm@kvack.org, linux-ia64@vger.kernel.org, Andi Kleen Christoph wrote: > This is an implementation that deals with monitoring and managing running > processes. So is this patch roughly equivalent to adding a pid to the mbind/set_mempolicy/get_mempolicy system calls? Not that I am advocating for or against adding doing that. But this seems like alot of code, with new and exciting API details, just to add a pid argument, if such it be. Andi - could you remind us all why you chose not to have a pid argument in these calls? -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson 1.925.600.0401