From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with SMTP id 1BCE06B01F0 for ; Fri, 13 Aug 2010 08:47:25 -0400 (EDT) Date: Fri, 13 Aug 2010 07:47:21 -0500 (CDT) From: Christoph Lameter Subject: Re: [PATCH 0/9] Hugepage migration (v2) In-Reply-To: <20100812075323.GA6112@spritzera.linux.bs1.fc.nec.co.jp> Message-ID: References: <1281432464-14833-1-git-send-email-n-horiguchi@ah.jp.nec.com> <20100812075323.GA6112@spritzera.linux.bs1.fc.nec.co.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Naoya Horiguchi Cc: Andi Kleen , Andrew Morton , Mel Gorman , Wu Fengguang , Jun'ichi Nomura , linux-mm , LKML List-ID: On Thu, 12 Aug 2010, Naoya Horiguchi wrote: > > Can you also avoid refcounts being increased during migration? > > Yes. I think this will be done in above-mentioned refactoring. Thats not what I meant. Can you avoid other processors increasing refcounts (direct I/O etc?) on any page struct of the huge page while migration is running? > This patch only handles migration under direct I/O. > For the opposite (direct I/O under migration) it's not true. > I wrote additional patches (later I'll reply to this email) > for solving locking problem. Could you review them? Sure. > (Maybe these patches are beyond the scope of hugepage migration patch, > so is it better to propose them separately?) Migration with known races is really not what we want in the kernel. -- 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/ . Don't email: email@kvack.org