From: Peter Zijlstra <peterz@infradead.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Christoph Lameter <cl@linux-foundation.org>,
"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: Mon, 14 May 2012 09:49:50 +0200 [thread overview]
Message-ID: <1336981790.2443.20.camel@twins> (raw)
In-Reply-To: <1336981501.2443.19.camel@twins>
On Mon, 2012-05-14 at 09:45 +0200, Peter Zijlstra wrote:
> On Mon, 2012-05-14 at 16:37 +0900, Minchan Kim wrote:
> > What's the meaning of "locked"? Isn't it pinning?
>
> It doesn't say, the best inference I can make is that locked means the
> effect of mlock() which is defined as: 'to be memory-resident', esp. so
> since it then states: 'until unlocked' (or exit/exec).
>
> So basically the statement: 'locked and memory-resident' is redundant.
And alternative interpretation of that statement is that mlock() whould
keep pages memory-resident, but also make them memory-resident. IE, it
should fault the entire range in before returning the system-call.
--
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-14 7:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 4:37 Allow migration of mlocked page? 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 [this message]
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
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=1336981790.2443.20.camel@twins \
--to=peterz@infradead.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=riel@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).