Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753515Ab2JUMby (ORCPT ); Sun, 21 Oct 2012 08:31:54 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:49357 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752929Ab2JUMbx (ORCPT ); Sun, 21 Oct 2012 08:31:53 -0400 Date: Sun, 21 Oct 2012 14:31:47 +0200 From: Ingo Molnar To: Rik van Riel Cc: Ni zhan Chen , Peter Zijlstra , Andrea Arcangeli , Linux Memory Management List , Mel Gorman , Linux kernel Mailing List Subject: Re: question on NUMA page migration Message-ID: <20121021123147.GB19229@gmail.com> References: <5081777A.8050104@redhat.com> <50836060.4050408@gmail.com> <5083608E.6040209@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5083608E.6040209@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 36 * Rik van Riel wrote: > On 10/20/2012 10:39 PM, Ni zhan Chen wrote: > >On 10/19/2012 11:53 PM, Rik van Riel wrote: > >>Hi Andrea, Peter, > >> > >>I have a question on page refcounting in your NUMA > >>page migration code. > >> > >>In Peter's case, I wonder why you introduce a new > >>MIGRATE_FAULT migration mode. If the normal page > >>migration / compaction logic can do without taking > >>an extra reference count, why does your code need it? > > > >Hi Rik van Riel, > > > >This is which part of codes? Why I can't find MIGRATE_FAULT in latest > >v3.7-rc2? > > It is in tip.git in the numa/core branch. The Git access URI is: git pull git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git numa/core git clone git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git numa/core Thanks, Ingo -- 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/