From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx116.postini.com [74.125.245.116]) by kanga.kvack.org (Postfix) with SMTP id D9C476B004A for ; Mon, 19 Mar 2012 05:58:36 -0400 (EDT) Message-ID: <4F670325.7080700@redhat.com> Date: Mon, 19 Mar 2012 11:57:57 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [RFC][PATCH 00/26] sched/numa References: <20120316144028.036474157@chello.nl> In-Reply-To: <20120316144028.036474157@chello.nl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: 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 On 03/16/2012 04:40 PM, Peter Zijlstra wrote: > The home-node migration handles both cpu and memory (anonymous only for now) in > an integrated fashion. The memory migration uses migrate-on-fault to avoid > doing a lot of work from the actual numa balancer kernl thread and only > migrates the active memory. > IMO, this needs to be augmented with eager migration, for the following reasons: - lazy migration adds a bit of latency to page faults - doesn't work well with large pages - doesn't work with dma engines So I think that in addition to migrate on fault we need a background thread to do eager migration. We might prioritize pages based on the active bit in the PDE (cheaper to clear and scan than the PTE, but gives less accurate information). -- error compiling committee.c: too many arguments to function -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org