Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756264Ab2F2Stk (ORCPT ); Fri, 29 Jun 2012 14:49:40 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38712 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755973Ab2F2Stj (ORCPT ); Fri, 29 Jun 2012 14:49:39 -0400 Message-ID: <4FEDF81C.1010401@redhat.com> Date: Fri, 29 Jun 2012 14:46:52 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Peter Zijlstra CC: dlaor@redhat.com, Ingo Molnar , Hillf Danton , Andrea Arcangeli , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Dan Smith , Linus Torvalds , Andrew Morton , Thomas Gleixner , Ingo Molnar , Paul Turner , Suresh Siddha , Mike Galbraith , "Paul E. McKenney" , Lai Jiangshan , Bharata B Rao , Lee Schermerhorn , Johannes Weiner , Srivatsa Vaddagiri , Christoph Lameter , Alex Shi , Mauricio Faria de Oliveira , Konrad Rzeszutek Wilk , Don Morris , Benjamin Herrenschmidt Subject: Re: [PATCH 13/40] autonuma: CPU follow memory algorithm References: <1340888180-15355-1-git-send-email-aarcange@redhat.com> <1340888180-15355-14-git-send-email-aarcange@redhat.com> <1340895238.28750.49.camel@twins> <20120629125517.GD32637@gmail.com> <4FEDDD0C.60609@redhat.com> <1340995260.28750.103.camel@twins> In-Reply-To: <1340995260.28750.103.camel@twins> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1437 Lines: 34 On 06/29/2012 02:41 PM, Peter Zijlstra wrote: > On Fri, 2012-06-29 at 12:51 -0400, Dor Laor wrote: >> t's hard to say whether Peter's like to add ia64 support or >> just like to get rid of the forceful migration as a whole. > > I've stated several times that all archs that have CONFIG_NUMA must be > supported before we can consider any of this. I've no intention of doing > so myself. Andrea wants this, Andrea gets to do it. I am not convinced all architectures that have CONFIG_NUMA need to be a requirement, since some of them (eg. Alpha) seem to be lacking a maintainer nowadays. It would be good if Andrea could touch base with the maintainers of the actively maintained architectures with NUMA, and get them to sign off on the way autonuma does things, and work with them to get autonuma ported to those architectures. > I've also stated several times that forceful migration in the context of > numa balancing must go. I am not convinced about this part either way. I do not see how a migration numa thread (which could potentially use idle cpu time) will be any worse than migrate on fault, which will always take away time from the userspace process. -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/