From: Eric B Munson <emunson@akamai.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Mike Marciniszyn <infinipath@intel.com>
Subject: Re: Resurrecting the VM_PINNED discussion
Date: Wed, 4 Mar 2015 09:45:45 -0500 [thread overview]
Message-ID: <20150304144544.GC6995@akamai.com> (raw)
In-Reply-To: <54F6303C.5080806@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
On Tue, 03 Mar 2015, Vlastimil Babka wrote:
<snip>
>
> No, you were correct and thanks for the hint. It's only ISOLATE_UNEVICTABLE from
> isolate_migratepages_range(), which is CMA, not regular compaction.
> But I wonder, can we change this even after VM_PINNED is introduced, if existing
> code depends on "no minor faults in mlocked areas", whatever the docs say? On
> the other hand, compaction is not the only source of migrations. I wonder what
> the NUMA balancing does (not) about mlocked areas...
My hope was that we could convince those that depend on mlock()
preventing minor faults to move to use the mpin() interface that was
discussed in the VM_PINNED thread. If that is not acceptable then we
really need to update the man page for mlock() and the vm documentation
to be very clear that minor faults are also prevented.
Eric
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-04 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:41 Eric B Munson
2015-03-03 18:35 ` Vlastimil Babka
2015-03-03 18:45 ` Eric B Munson
2015-03-03 19:51 ` Christoph Lameter
2015-03-03 20:20 ` Vlastimil Babka
2015-03-03 20:22 ` Christoph Lameter
2015-03-03 21:01 ` Eric B Munson
2015-03-03 21:52 ` Eric B Munson
2015-03-03 22:05 ` Vlastimil Babka
2015-03-04 14:45 ` Eric B Munson [this message]
2015-03-03 19:13 ` Davidlohr Bueso
2015-03-05 20:46 ` Peter Zijlstra
2015-03-05 21:09 ` Christoph Lameter
2015-03-05 21:13 ` Peter Zijlstra
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=20150304144544.GC6995@akamai.com \
--to=emunson@akamai.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hal.rosenstock@gmail.com \
--cc=hughd@google.com \
--cc=infinipath@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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