From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-f48.google.com (mail-ee0-f48.google.com [74.125.83.48]) by kanga.kvack.org (Postfix) with ESMTP id DB9A66B0036 for ; Tue, 6 May 2014 12:31:26 -0400 (EDT) Received: by mail-ee0-f48.google.com with SMTP id e49so5442213eek.7 for ; Tue, 06 May 2014 09:31:26 -0700 (PDT) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTP id v2si13875876eel.16.2014.05.06.09.31.24 for ; Tue, 06 May 2014 09:31:25 -0700 (PDT) Message-ID: <53690E29.7060602@redhat.com> Date: Tue, 06 May 2014 12:30:33 -0400 From: Rik van Riel MIME-Version: 1.0 Subject: Re: [RFC] Heterogeneous memory management (mirror process address space on a device mmu). References: <1399038730-25641-1-git-send-email-j.glisse@gmail.com> <20140506102925.GD11096@twins.programming.kicks-ass.net> <20140506150014.GA6731@gmail.com> <20140506153315.GB6731@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Linus Torvalds , Jerome Glisse Cc: Peter Zijlstra , linux-mm , Linux Kernel Mailing List , linux-fsdevel , Mel Gorman , "H. Peter Anvin" , Andrew Morton , Linda Wang , Kevin E Martin , Jerome Glisse , Andrea Arcangeli , Johannes Weiner , Larry Woodman , Dave Airlie , Jeff Law , Brendan Conoboy , Joe Donohue , Duncan Poole , Sherry Cheung , Subhash Gutti , John Hubbard , Mark Hairgrove , Lucien Dunning , Cameron Buschardt , Arvind Gopalakrishnan , Haggai Eran , Or Gerlitz , Sagi Grimberg , Shachar Raindel , Liran Liss , Roland Dreier , "Sander, Ben" , "Stoner, Greg" , "Bridgman, John" , "Mantor, Michael" , "Blinzer, Paul" , "Morichetti, Laurent" , "Deucher, Alexander" , "Gabbay, Oded" , Davidlohr Bueso On 05/06/2014 11:47 AM, Linus Torvalds wrote: > And as I've mentioned, there is a correct place to slot this in, and > that correct way is the _only_ way to ever support future GPU's that > _do_ share direct access to the page tables. The GPU runs a lot faster when using video memory, instead of system memory, on the other side of the PCIe bus. The CPU cannot directly address video memory. How can shared page table access work, given these constraints? -- All rights reversed -- 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: email@kvack.org