linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-mm@kvack.org, linux-pm@lists.osdl.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	mark.gross@intel.com, neelam.chandwani@intel.com
Subject: Re: [RFC] [PATCH] Power Managed memory base enabling
Date: Tue, 6 Mar 2007 09:33:50 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703060925550.27341@chino.kir.corp.google.com> (raw)
In-Reply-To: <20070306172039.GA26038@linux.intel.com>

On Tue, 6 Mar 2007, Mark Gross wrote:

> > Is do_migrate_pages() currently unsatisfactory for this?
> 
> This looks like it should be good for this application!  How stable is
> this?  The next phase of this work is to export the policy interfaces
> and hook up the page migration.  I'm somewhat new to the mm code.
> 

Since you've already used a NUMA approach to flagging PM-memory, you'd 
probably want to use this interface through mempolicy in your migration.  
There's currently work to do lockless VMA scanning that was posted just 
yesterday to linux-mm and that's a bottleneck in this migration.

Take a look at update_nodemask() in kernel/cpuset.c for how it migrates 
pages from a source set of nodes to a destination set using 
memory_migrate.  The cpuset specifics are explained in 
Documentation/cpusets.txt, but the basics are that you'll want to use 
memory_migrate to start the migration when you remove a node from your 
nodemask (another reason why I suggested the use of a nodemask instead of 
a simple array).

		David

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-03-06 17:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 18:18 Mark Gross
2007-03-06  1:26 ` KAMEZAWA Hiroyuki
2007-03-06 15:54   ` Mark Gross
2007-03-06 15:09 ` David Rientjes
2007-03-06 16:47   ` Mark Gross
2007-03-06 17:12     ` David Rientjes
2007-03-06 17:20       ` Mark Gross
2007-03-06 17:33         ` David Rientjes [this message]
2007-03-07  2:40     ` David Rientjes
2007-03-09 20:53       ` Mark Gross
2007-03-09 21:27         ` David Rientjes
2007-03-09 21:26           ` Mark Gross
2007-03-26 12:48 ` [linux-pm] " Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0703060925550.27341@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mark.gross@intel.com \
    --cc=mgross@linux.intel.com \
    --cc=neelam.chandwani@intel.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox