Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261294AbVBNWXj (ORCPT ); Mon, 14 Feb 2005 17:23:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261323AbVBNWXj (ORCPT ); Mon, 14 Feb 2005 17:23:39 -0500 Received: from e32.co.us.ibm.com ([32.97.110.130]:6623 "EHLO e32.co.us.ibm.com") by vger.kernel.org with ESMTP id S261294AbVBNWXh (ORCPT ); Mon, 14 Feb 2005 17:23:37 -0500 Subject: Re: [RFC 2.6.11-rc2-mm2 7/7] mm: manual page migration -- sys_page_migrate From: Dave Hansen To: Robin Holt Cc: Ray Bryant , Hirokazu Takahashi , Hugh DIckins , Andrew Morton , Marcello Tosatti , Ray Bryant , linux-mm , linux-kernel In-Reply-To: <20050214220148.GA11832@lnx-holt.americas.sgi.com> References: <20050212032535.18524.12046.26397@tomahawk.engr.sgi.com> <20050212032620.18524.15178.29731@tomahawk.engr.sgi.com> <1108242262.6154.39.camel@localhost> <20050214135221.GA20511@lnx-holt.americas.sgi.com> <1108407043.6154.49.camel@localhost> <20050214220148.GA11832@lnx-holt.americas.sgi.com> Content-Type: text/plain Date: Mon, 14 Feb 2005 14:22:54 -0800 Message-Id: <1108419774.6154.58.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1318 Lines: 30 On Mon, 2005-02-14 at 16:01 -0600, Robin Holt wrote: > On Mon, Feb 14, 2005 at 10:50:42AM -0800, Dave Hansen wrote: > > On Mon, 2005-02-14 at 07:52 -0600, Robin Holt wrote: > > > The node mask is a list of allowed. This is intended to be as near > > > to a one-to-one migration path as possible. > > > > If that's the case, it would make the kernel internals a bit simpler to > > only take a "from" and "to" node, instead of those maps. You'll end up > > making multiple syscalls, but that shouldn't be a problem. > > Then how do you handle overlapping nodes. If I am doing a 5->4, 4->3, > 3->2, 2->1 shift in the memory placement and had only a from and to node, > I would end up calling multiple times. This would end up in memory shifting > from 5->4 on the first, 4->3 on the second, ... with the end result of > all memory shifting to a single node. Can you give an example of when you'd actually want to do this? > On a seperate topic, I would guess the syscall time is trivial compared > to the time to walk the page tables. I'd certainly agree. -- Dave - 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/