From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 5 Feb 2008 13:03:07 -0800 (PST) From: David Rientjes Subject: Re: [2.6.24-rc8-mm1][regression?] numactl --interleave=all doesn't works on memoryless node. In-Reply-To: <20080205145141.ae658c12.pj@sgi.com> Message-ID: References: <20080202165054.F491.KOSAKI.MOTOHIRO@jp.fujitsu.com> <20080202090914.GA27723@one.firstfloor.org> <20080202180536.F494.KOSAKI.MOTOHIRO@jp.fujitsu.com> <1202149243.5028.61.camel@localhost> <20080205041755.3411b5cc.pj@sgi.com> <20080205145141.ae658c12.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Paul Jackson Cc: Lee.Schermerhorn@hp.com, kosaki.motohiro@jp.fujitsu.com, andi@firstfloor.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, clameter@sgi.com, mel@csn.ul.ie List-ID: On Tue, 5 Feb 2008, Paul Jackson wrote: > David wrote: > > The more alarming result of these remaps is in the MPOL_BIND case, as > > we've talked about before. The language in set_mempolicy(2): > > You're diving into the middle of a rather involved discussion > we had on the other various patches proposed to extend the > interaction of mempolicy's with cpusets and hotplug. > I've simply identified that MPOL_BIND mempolicy interactions with a task's changing mems_allowed as a result of a cpuset move or mems change is also an issue that can be addressed at the same time as the interleave problem. And it can be done with the addition of a single MPOL_F_* flag. > I choose not to hijack this current thread with my rebuttal, > which you've seen before, of your points here. > The issues of mempolicies working over memoryless nodes and supporting changing cpusets are very closely related and can be addressed in the same way. It would be disappointing to see a lot of work done to fix the memoryless node issue or the changing cpuset mems issue and then realize both could have been fixed quite simply with a relatively small set of changes. David -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org