From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030473Ab2CSNyG (ORCPT ); Mon, 19 Mar 2012 09:54:06 -0400 Received: from smtp109.prem.mail.ac4.yahoo.com ([76.13.13.92]:25956 "HELO smtp109.prem.mail.ac4.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754090Ab2CSNyE (ORCPT ); Mon, 19 Mar 2012 09:54:04 -0400 X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: IbGsImMVM1lfEkDimj.2BnXR1mH9oiPl1XBtbiV1lALYFlj uKbrB7ZViKxil4vLnD4Z2IsmBkG3cmQsNlOz1zL7npEFW7hShdy_IidX78hZ jvEGCgf4y32PJuvF3YjwBPce8JUJXWSeTIEbjfwt3K5wGBpKo4ZIaG_XBoF. dzWF9z2cfQsl65mnWYErMLgRc6q4.8KlzjVmQatKWmjfpF5zoOWSGhREnJml Ni4fqb2g1fgAoByYuoetSs8Dy4k4eZwbJSVFuxKseoi2dCuHmmDryGB8buBE 7AZRgx9NCJNZABmTjaQfijAfih0wglnTSpxGzna6G0f6M2GHj56cAoieu_x6 gioRh6n0TUMBR0ld1XVuOZziz7GKl1f.sQ93xMES.g7yoS4i3QN8DN2jLuJt A08S_X3fR6.nGp4sgdH.Kw80UPN2nQzCI7yvS X-Yahoo-SMTP: _Dag8S.swBC1p4FJKLCXbs8NQzyse1SYSgnAbY0- Date: Mon, 19 Mar 2012 08:53:57 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@router.home To: Peter Zijlstra 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 Subject: Re: [RFC][PATCH 10/26] mm, mpol: Make mempolicy home-node aware In-Reply-To: <1331932375.18960.237.camel@twins> Message-ID: References: <20120316144028.036474157@chello.nl> <20120316144240.763518310@chello.nl> <1331932375.18960.237.camel@twins> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.