From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Jackson Date: Sun, 17 Jul 2005 07:22:41 +0000 Subject: Re: [NUMA] Display and modify the memory policy of a process Message-Id: <20050717002241.3224f104.pj@sgi.com> List-Id: References: <20050715214700.GJ15783@wotan.suse.de> <20050715220753.GK15783@wotan.suse.de> <20050715223756.GL15783@wotan.suse.de> <20050715225635.GM15783@wotan.suse.de> <20050715234402.GN15783@wotan.suse.de> <20050716020141.GO15783@wotan.suse.de> <20050716163030.0147b6ba.pj@sgi.com> <20050716205038.48c05e96.pj@sgi.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Christoph Lameter Cc: ak@suse.de, kenneth.w.chen@intel.com, linux-mm@kvack.org, linux-ia64@vger.kernel.org Christoph, responding to pj: > > I'm missing something here. Are you saying that just a change to > > libnuma would suffice to accomplish what you sought with this patch? > > Its a quite significant change but yes of course you can do that ... I am totally stumped. I have no idea how what you have in mind. The mbind, set_mempolicy and get_mempolicy system calls plainly and simply apply only to the current task, and it would take changes in kernel code and the system call API to change that fact in any sensible way. You've dropped one hint: its a quite significant change. If you have the patience, could you drop a couple more hints on how to do this (make this change by just changing libnuma)? Perhaps with a little more technical meat on their bones? -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson 1.925.600.0401