From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755909AbbCEVNX (ORCPT ); Thu, 5 Mar 2015 16:13:23 -0500 Received: from casper.infradead.org ([85.118.1.10]:41368 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752570AbbCEVNV (ORCPT ); Thu, 5 Mar 2015 16:13:21 -0500 Date: Thu, 5 Mar 2015 22:13:06 +0100 From: Peter Zijlstra To: Christoph Lameter Cc: Eric B Munson , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Andrew Morton , Hugh Dickins , Mel Gorman , Roland Dreier , Sean Hefty , Hal Rosenstock , Mike Marciniszyn Subject: Re: Resurrecting the VM_PINNED discussion Message-ID: <20150305211306.GV21418@twins.programming.kicks-ass.net> References: <20150303174105.GA3295@akamai.com> <20150305204632.GT21418@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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.