Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965068AbbD0Tf1 (ORCPT ); Mon, 27 Apr 2015 15:35:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33551 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964816AbbD0Tf0 (ORCPT ); Mon, 27 Apr 2015 15:35:26 -0400 Message-ID: <553E8F75.5060502@redhat.com> Date: Mon, 27 Apr 2015 15:35:17 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Christoph Lameter , Jerome Glisse CC: "Paul E. McKenney" , Benjamin Herrenschmidt , linux-kernel@vger.kernel.org, linux-mm@kvack.org, jglisse@redhat.com, mgorman@suse.de, aarcange@redhat.com, airlied@redhat.com, aneesh.kumar@linux.vnet.ibm.com, Cameron Buschardt , Mark Hairgrove , Geoffrey Gerfin , John McKenna , akpm@linux-foundation.org Subject: Re: Interacting with coherent memory on external devices References: <20150424171957.GE3840@gmail.com> <20150424192859.GF3840@gmail.com> <20150425114633.GI5561@linux.vnet.ibm.com> <20150427154728.GA26980@gmail.com> <20150427164325.GB26980@gmail.com> <20150427172143.GC26980@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1134 Lines: 26 On 04/27/2015 03:26 PM, Christoph Lameter wrote: > DAX is about directly accessing memory. It is made for the purpose of > serving as a block device for a filesystem right now but it can easily be > used as a way to map any external memory into a processes space using the > abstraction of a block device. But then you can do that with any device > driver using VM_PFNMAP or VM_MIXEDMAP. Maybe we better use that term > instead. Guess I have repeated myself 6 times or so now? I am stopping > with this one. Yeah, please stop. If after 6 times you have still not grasped that having the application manage which memory goes onto the device and which goes in RAM is the exact opposite of the use model that Paul and Jerome are trying to enable (transparent moving around of memory, by eg. GPU calculation libraries), you are clearly not paying enough attention. -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/