Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751959AbaKKTBF (ORCPT ); Tue, 11 Nov 2014 14:01:05 -0500 Received: from resqmta-ch2-09v.sys.comcast.net ([69.252.207.41]:60060 "EHLO resqmta-ch2-09v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751671AbaKKTBB (ORCPT ); Tue, 11 Nov 2014 14:01:01 -0500 Date: Tue, 11 Nov 2014 13:00:56 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: j.glisse@gmail.com cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds , joro@8bytes.org, Mel Gorman , "H. Peter Anvin" , Peter Zijlstra , Andrea Arcangeli , Johannes Weiner , Larry Woodman , Rik van Riel , Dave Airlie , Brendan Conoboy , Joe Donohue , Duncan Poole , Sherry Cheung , Subhash Gutti , John Hubbard , Mark Hairgrove , Lucien Dunning , Cameron Buschardt , Arvind Gopalakrishnan , Shachar Raindel , Liran Liss , Roland Dreier , Ben Sander , Greg Stoner , John Bridgman , Michael Mantor , Paul Blinzer , Laurent Morichetti , Alexander Deucher , Oded Gabbay , linux-fsdevel@vger.kernel.org, Linda Wang , Kevin E Martin , Jerome Glisse , Jeff Law , Haggai Eran , Or Gerlitz , Sagi Grimberg Subject: Re: HMM (heterogeneous memory management) v6 In-Reply-To: <1415644096-3513-1-git-send-email-j.glisse@gmail.com> Message-ID: References: <1415644096-3513-1-git-send-email-j.glisse@gmail.com> 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 Mon, 10 Nov 2014, j.glisse@gmail.com wrote: > In a nutshell HMM is a subsystem that provide an easy to use api to mirror a > process address on a device with minimal hardware requirement (mainly device > page fault and read only page mapping). This does not rely on ATS and PASID > PCIE extensions. It intends to supersede those extensions by allowing to move > system memory to device memory in a transparent fashion for core kernel mm > code (ie cpu page fault on page residing in device memory will trigger > migration back to system memory). Could we define a new NUMA node that maps memory from the GPU and then simply use the existing NUMA features to move a process over there. -- 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/