[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150305211306.GV21418@twins.programming.kicks-ass.net>
Date: Thu, 5 Mar 2015 22:13:06 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Christoph Lameter <cl@...ux.com>
Cc: Eric B Munson <emunson@...mai.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Hugh Dickins <hughd@...gle.com>, Mel Gorman <mgorman@...e.de>,
Roland Dreier <roland@...nel.org>,
Sean Hefty <sean.hefty@...el.com>,
Hal Rosenstock <hal.rosenstock@...il.com>,
Mike Marciniszyn <infinipath@...el.com>
Subject: Re: Resurrecting the VM_PINNED discussion
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists