From: Peter Zijlstra <peterz@infradead.org>
To: Christoph Lameter <cl@linux.com>
Cc: Eric B Munson <emunson@akamai.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.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: Thu, 5 Mar 2015 22:13:06 +0100 [thread overview]
Message-ID: <20150305211306.GV21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1503051508130.790@gentwo.org>
On Thu, Mar 05, 2015 at 03:09:42PM -0600, Christoph Lameter wrote:
> On Thu, 5 Mar 2015, Peter Zijlstra wrote:
>
> > > Am I missing something about why it was never merged?
> >
> > Because I got lost in IB code and didn't manage to bribe anyone into
> > fixing that for me.
>
> Well the complexity increased since then with the on demand pinning,
> mmu notifiers etc etc ...
Clearly I've not been paying attention, what? Is this that drug induced
stuff benh was babbling about a while back?
> I thought the clear distinction between pinning and mlocking would do the
> trick?
Nah, it still leaves the accounting up shit creek.
--
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>
prev parent reply other threads:[~2015-03-05 21:13 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
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 [this message]
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=20150305211306.GV21418@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--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=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=tglx@linutronix.de \
/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