From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031025Ab2CSOGu (ORCPT ); Mon, 19 Mar 2012 10:06:50 -0400 Received: from casper.infradead.org ([85.118.1.10]:43128 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964937Ab2CSOGt convert rfc822-to-8bit (ORCPT ); Mon, 19 Mar 2012 10:06:49 -0400 Message-ID: <1332165959.18960.340.camel@twins> Subject: Re: [RFC][PATCH 10/26] mm, mpol: Make mempolicy home-node aware From: Peter Zijlstra To: Christoph Lameter Cc: Linus Torvalds , Andrew Morton , Thomas Gleixner , Ingo Molnar , Paul Turner , Suresh Siddha , Mike Galbraith , "Paul E. McKenney" , Lai Jiangshan , Dan Smith , Bharata B Rao , Lee Schermerhorn , Andrea Arcangeli , Rik van Riel , Johannes Weiner , linux-kernel@vger.kernel.org, linux-mm@kvack.org Date: Mon, 19 Mar 2012 15:05:59 +0100 In-Reply-To: References: <20120316144028.036474157@chello.nl> <20120316144240.763518310@chello.nl> <1331932375.18960.237.camel@twins> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-03-19 at 08:53 -0500, Christoph Lameter wrote: > On Fri, 16 Mar 2012, Peter Zijlstra wrote: > > > > > Note that the tsk_home_node() policy has Migrate-on-Fault enabled to > > > > facilitate efficient on-demand memory migration. > > > > > > The numa hierachy is already complex. Could we avoid adding another layer > > > by adding a MPOL_HOME_NODE and make that the default? > > > > Not sure that's really a win, the behaviour would be the same we just > > have to implement another policy, which is likely more code. > > A HOME_NODE policy would also help to ensure that existing applications > continue to work as expected. Given that people in the HPC industry and > elsewhere have been fine tuning around the scheduler for years this is a > desirable goal and ensures backward compatibility. I really have no idea what you're saying. Existing applications that use mbind/set_mempolicy already continue to function exactly like before, see how the new layer is below all that.