From: Christoph Lameter <cl@linux.com>
To: Eric B Munson <emunson@akamai.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
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: Tue, 3 Mar 2015 13:51:12 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.11.1503031349360.15876@gentwo.org> (raw)
In-Reply-To: <20150303184520.GA4996@akamai.com>
On Tue, 3 Mar 2015, Eric B Munson wrote:
> > So you are saying that mlocking (VM_LOCKED) prevents migration and thus
> > compaction to do its job? If that's true, I think it's a bug as it is AFAIK
> > supposed to work just fine.
>
> Agreed. But as has been discussed in the threads around the VM_PINNED
> work, there are people that are relying on the fact that VM_LOCKED
> promises no minor faults. Which is why the behavoir has remained.
AFAICT mlocking preventing migration is something that could be taken out.
Google removes the restriction.
mlocked does not promise no minor faults only that the page will stay
resident. The pinning results in no faults.
> VM_PINNED itself doesn't help us, but it would allow us to make
> VM_LOCKED use only the weaker 'no major fault' semantics while still
> providing a way for anyone that needs the stronger 'no minor fault'
> promise to get the semantics they need.
The semantics for mlock allow migration and therefore defrag as well as
thp processing.
--
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:[~2015-03-03 19:51 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 [this message]
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
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=alpine.DEB.2.11.1503031349360.15876@gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=emunson@akamai.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