From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945948AbbCEVJq (ORCPT ); Thu, 5 Mar 2015 16:09:46 -0500 Received: from resqmta-ch2-10v.sys.comcast.net ([69.252.207.42]:51386 "EHLO resqmta-ch2-10v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756281AbbCEVJo (ORCPT ); Thu, 5 Mar 2015 16:09:44 -0500 Date: Thu, 5 Mar 2015 15:09:42 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Peter Zijlstra 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 In-Reply-To: <20150305204632.GT21418@twins.programming.kicks-ass.net> Message-ID: References: <20150303174105.GA3295@akamai.com> <20150305204632.GT21418@twins.programming.kicks-ass.net> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 ... I thought the clear distinction between pinning and mlocking would do the trick?