From: Christoph Lameter <clameter@sgi.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, ak@suse.de, pj@sgi.com, kravetz@us.ibm.com,
marcelo.tosatti@cyclades.com, taka@valinux.co.jp,
lee.schermerhorn@hp.com, haveblue@us.ibm.com
Subject: Re: Status and the future of page migration
Date: Thu, 11 May 2006 20:21:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0605112017040.17677@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060512110825.7a49f17d.kamezawa.hiroyu@jp.fujitsu.com>
On Fri, 12 May 2006, KAMEZAWA Hiroyuki wrote:
> Hmm...it seems the kernel drivers assumes the pages will not moved if VM_LOCKED.
> I'm not sure which is better to replace all driver's VM_LOCKED to VM_DONTMOVE or
> to add VM_KEEPONMEMORY for mlock() codes and just modify the kernel core.
We could add a MCL_DONTMOVE to mlockall() because we need also some way
for user space to pin pages and then add a VM_DONTMOVE to the vm
flags. Then do a global search through the kernel source and replace
VM_LOCKED in the drivers with VM_DONTMOVE.
--
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>
prev parent reply other threads:[~2006-05-12 3:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 0:06 Christoph Lameter
2006-05-12 0:56 ` KAMEZAWA Hiroyuki
2006-05-12 1:06 ` Christoph Lameter
2006-05-12 1:35 ` KAMEZAWA Hiroyuki
2006-05-12 1:43 ` Christoph Lameter
2006-05-12 2:08 ` KAMEZAWA Hiroyuki
2006-05-12 3:21 ` Christoph Lameter [this message]
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.0605112017040.17677@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=ak@suse.de \
--cc=haveblue@us.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kravetz@us.ibm.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=pj@sgi.com \
--cc=taka@valinux.co.jp \
/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