From: Christoph Lameter <cl@linux.com>
To: Roland Dreier <roland@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
tglx@linutronix.de, Ingo Molnar <mingo@redhat.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: Allow migration of mlocked page?
Date: Tue, 15 May 2012 09:27:47 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1205150922050.6488@router.home> (raw)
In-Reply-To: <CAG4TOxOdBkdobs95EPvVNKEAk-S8A_Rs_Rdy3Ky+TTtS1sRukg@mail.gmail.com>
On Mon, 14 May 2012, Roland Dreier wrote:
> In any case I don't see any problem with doing vma splitting in
> drivers/core/infiniband/umem.c if need be.
Prohibiting migration is already supported at the VMA level. There is no
need to add anyting extra.
"struct vm_operations_struct" has a field for the "migrate" function.
If that field is set to "fail_migrate_page" then no migration will ever
take place on the VMA.
But this feature is not accessible from user space. So far it has
only been used by special filesystesm.
And disabling migration does not solve the "I want no faults
whatsovever" requirement that I keep hearing.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-15 14:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 4:37 Minchan Kim
2012-05-11 9:20 ` Peter Zijlstra
2012-05-11 16:20 ` Christoph Lameter
2012-05-11 23:24 ` KOSAKI Motohiro
2012-05-14 13:45 ` Christoph Lameter
2012-05-14 4:13 ` Minchan Kim
2012-05-14 6:56 ` Peter Zijlstra
2012-05-14 7:37 ` Minchan Kim
2012-05-14 7:45 ` Peter Zijlstra
2012-05-14 7:49 ` Peter Zijlstra
2012-05-14 7:54 ` Minchan Kim
2012-05-14 13:47 ` Christoph Lameter
2012-05-15 1:23 ` Minchan Kim
2012-05-15 11:07 ` Peter Zijlstra
2012-05-11 13:14 ` Mel Gorman
2012-05-11 23:25 ` KOSAKI Motohiro
2012-05-14 13:32 ` Mel Gorman
2012-05-14 13:51 ` Peter Zijlstra
2012-05-14 14:01 ` Christoph Lameter
2012-05-14 14:14 ` Peter Zijlstra
2012-05-14 14:43 ` Christoph Lameter
2012-05-14 22:52 ` KOSAKI Motohiro
2012-05-14 23:04 ` Roland Dreier
2012-05-15 14:27 ` Christoph Lameter [this message]
2012-05-15 1:38 ` Minchan Kim
2012-05-14 14:08 ` Peter Zijlstra
2012-05-14 23:06 ` KOSAKI Motohiro
2012-05-15 1:35 ` Minchan Kim
2012-05-14 4:25 ` Minchan Kim
2012-05-14 13:39 ` Mel Gorman
2012-05-15 2:15 ` Minchan Kim
2012-05-15 4:33 ` KOSAKI Motohiro
2012-05-15 11:06 ` Peter Zijlstra
2012-05-15 14:12 ` Christoph Lameter
2012-05-15 14:45 ` Peter Zijlstra
2012-05-15 15:11 ` Christoph Lameter
2012-05-15 14:10 ` Christoph Lameter
2012-05-15 14:09 ` Christoph Lameter
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=alpine.DEB.2.00.1205150922050.6488@router.home \
--to=cl@linux.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=roland@kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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