From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: Allow migration of mlocked pages
Date: Wed, 24 May 2006 16:45:24 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0605241640010.16435@blonde.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605240824050.15446@schroedinger.engr.sgi.com>
On Wed, 24 May 2006, Christoph Lameter wrote:
>
> I ran a test program that mlocked an array of pages and then migrated it
> via sys_move_pages() and then verified what happened. Will run some more
> stress tests today.
>
> ldso and glibc create some mlocked pages for each binary. If we do
> migration with MPOL_MF_MOVE_ALL (common way of migrating pages) then
> we usually will have to migrate VM_LOCKED pages of ldso and glibc. So
> almost any testng of page migration will invariably involve migration of
> VM_LOCKED pages.
Oh, I'm not worried about whether ordinary VM_LOCKED pages will get
migrated properly, I can't see any problem with that. It's whether
something somewhere is using mlock and somehow relying on the
physical pages to be pinned. I don't know what form that "somehow"
would take, and I'm not saying there is or can be any such thing:
just worried that we want wide exposure yet few testers migrate.
Hugh
--
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>
next prev parent reply other threads:[~2006-05-24 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 1:15 Christoph Lameter
2006-05-24 15:23 ` Hugh Dickins
2006-05-24 15:30 ` Christoph Lameter
2006-05-24 15:45 ` Hugh Dickins [this message]
2006-05-24 16:09 ` Christoph Lameter
2006-05-24 20:37 ` Hugh Dickins
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.0605241640010.16435@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.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