Message-Id: <1445461210-2605-1-git-send-email-jglisse@redhat.com>
Date:	Wed, 21 Oct 2015 16:59:55 -0400
From:	Jérôme Glisse <jglisse@...hat.com>
To:	akpm@...ux-foundation.org, <linux-kernel@...r.kernel.org>,
	linux-mm@...ck.org
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>, <joro@...tes.org>,
	Mel Gorman <mgorman@...e.de>, "H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Johannes Weiner <jweiner@...hat.com>,
	Larry Woodman <lwoodman@...hat.com>,
	Rik van Riel <riel@...hat.com>,
	Dave Airlie <airlied@...hat.com>,
	Brendan Conoboy <blc@...hat.com>,
	Joe Donohue <jdonohue@...hat.com>,
	Christophe Harle <charle@...dia.com>,
	Duncan Poole <dpoole@...dia.com>,
	Sherry Cheung <SCheung@...dia.com>,
	Subhash Gutti <sgutti@...dia.com>,
	John Hubbard <jhubbard@...dia.com>,
	Mark Hairgrove <mhairgrove@...dia.com>,
	Lucien Dunning <ldunning@...dia.com>,
	Cameron Buschardt <cabuschardt@...dia.com>,
	Arvind Gopalakrishnan <arvindg@...dia.com>,
	Haggai Eran <haggaie@...lanox.com>,
	Shachar Raindel <raindel@...lanox.com>,
	Liran Liss <liranl@...lanox.com>,
	Roland Dreier <roland@...estorage.com>,
	Ben Sander <ben.sander@....com>,
	Greg Stoner <Greg.Stoner@....com>,
	John Bridgman <John.Bridgman@....com>,
	Michael Mantor <Michael.Mantor@....com>,
	Paul Blinzer <Paul.Blinzer@....com>,
	Leonid Shamis <Leonid.Shamis@....com>,
	Laurent Morichetti <Laurent.Morichetti@....com>,
	Alexander Deucher <Alexander.Deucher@....com>,
	"Linda Wang" <lwang@...hat.com>, "Kevin E Martin" <kem@...hat.com>,
	"Jeff Law" <law@...hat.com>, "Or Gerlitz" <ogerlitz@...lanox.com>,
	"Sagi Grimberg" <sagig@...lanox.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: [PATCH v11 00/15] HMM (Heterogeneous Memory Management)

Minor fixes since last post (1), apply on top of 4.3rc6.
Please consider applying. Tree with the patchset:

git://people.freedesktop.org/~glisse/linux hmm-v11 branch

HMM (HMM (Heterogeneous Memory Management) is an helper layer
for device driver, its main features are :
   - Shadow CPU page table of a process into a device specific
     format page table and keep both page table synchronize.
   - Handle DMA mapping of system ram page on behalf of device
     (for shadowed page table entry).
   - Migrate private anonymous memory to private device memory
     and handle CPU page fault (which triggers a migration back
     to system memory so CPU can access it).

Benefits of HMM :
   - Avoid current model where device driver have to pin page
     which blocks several kernel features (KSM, migration, ...).
   - No impact on existing workload that do not use HMM (it only
     adds couple more if() to common code path).
   - Intended as common infrastructure for several different
     hardware, as of today Mellanox and NVidia.
   - Allow userspace API to move away from explicit copy code
     path where application programmer has to manage manually
     memcpy to and from device memory.
   - Transparent to userspace, for instance allowing library to
     use GPU without involving application linked against it.

I expect other hardware company to express interest in HMM and
eventualy start using it with their new hardware. I give a more
in depth motivation after the change log.


Change log :

v11:
  - Fix PROT_NONE case.
  - Fix missing page table walk callback.
  - Add support for hugetlbfs.

v10:
  - Minor fixes here and there.

v9:
  - Added new device driver helpers.
  - Added documentions.
  - Improved page table code claritity (minor architectural changes
    and better names).

v8:
  - Removed currently unuse fence code.
  - Added DMA mapping on behalf of device.

v7:
  - Redone and simplified page table code to match Linus suggestion
    http://article.gmane.org/gmane.linux.kernel.mm/125257

... Lost in translation ...


Why doing this ?

Mirroring a process address space is mandatory with OpenCL 2.0 and
with other GPU compute APIs. OpenCL 2.0 allows different level of
implementation and currently only the lowest 2 are supported on
Linux. To implement the highest level, where CPU and GPU access
can happen concurently and are cache coherent, HMM is needed, or
something providing same functionality, for instance through
platform hardware.

Hardware solution such as PCIE ATS/PASID is limited to mirroring
system memory and does not provide way to migrate memory to device
memory (which offer significantly more bandwidth, up to 10 times
faster than regular system memory with discrete GPU, also have
lower latency than PCIE transaction).

Current CPU with GPU on same die (AMD or Intel) use the ATS/PASID
and for Intel a special level of cache (backed by a large pool of
fast memory).

For foreseeable future, discrete GPUs will remain releveant as they
can have a large quantity of faster memory than integrated GPU.

Thus we believe HMM will allow us to leverage discrete GPUs memory
in a transparent fashion to the application, with minimum disruption
to the linux kernel mm code. Also HMM can work along hardware
solution such as PCIE ATS/PASID (leaving regular case to ATS/PASID
while HMM handles the migrated memory case).


Design :

The patch 1, 2, 3 and 4 augment the mmu notifier API with new
informations to more efficiently mirror CPU page table updates.

The first side of HMM, process address space mirroring, is
implemented in patch 5 through 14. This use a secondary page
table, in which HMM mirror memory actively use by the device.
HMM does not take a reference on any of the page, it use the
mmu notifier API to track changes to the CPU page table and to
update the mirror page table. All this while providing a simple
API to device driver.

To implement this we use a "generic" page table and not a radix
tree because we need to store more flags than radix allows and
we need to store dma address (sizeof(dma_addr_t) > sizeof(long)
on some platform).


(1) Previous patchset posting :
    v1 http://lwn.net/Articles/597289/
    v2 https://lkml.org/lkml/2014/6/12/559
    v3 https://lkml.org/lkml/2014/6/13/633
    v4 https://lkml.org/lkml/2014/8/29/423
    v5 https://lkml.org/lkml/2014/11/3/759
    v6 http://lwn.net/Articles/619737/
    v7 http://lwn.net/Articles/627316/
    v8 https://lwn.net/Articles/645515/
    v9 https://lwn.net/Articles/651553/
    v10 https://lwn.net/Articles/654430/

Cheers,
Jérôme

To: "Andrew Morton" <akpm@...ux-foundation.org>,
To: <linux-kernel@...r.kernel.org>,
To: linux-mm <linux-mm@...ck.org>,
Cc: "Linus Torvalds" <torvalds@...ux-foundation.org>,
Cc: "Mel Gorman" <mgorman@...e.de>,
Cc: "H. Peter Anvin" <hpa@...or.com>,
Cc: "Peter Zijlstra" <peterz@...radead.org>,
Cc: "Linda Wang" <lwang@...hat.com>,
Cc: "Kevin E Martin" <kem@...hat.com>,
Cc: "Andrea Arcangeli" <aarcange@...hat.com>,
Cc: "Johannes Weiner" <jweiner@...hat.com>,
Cc: "Larry Woodman" <lwoodman@...hat.com>,
Cc: "Rik van Riel" <riel@...hat.com>,
Cc: "Dave Airlie" <airlied@...hat.com>,
Cc: "Jeff Law" <law@...hat.com>,
Cc: "Brendan Conoboy" <blc@...hat.com>,
Cc: "Joe Donohue" <jdonohue@...hat.com>,
Cc: "Christophe Harle" <charle@...dia.com>,
Cc: "Duncan Poole" <dpoole@...dia.com>,
Cc: "Sherry Cheung" <SCheung@...dia.com>,
Cc: "Subhash Gutti" <sgutti@...dia.com>,
Cc: "John Hubbard" <jhubbard@...dia.com>,
Cc: "Mark Hairgrove" <mhairgrove@...dia.com>,
Cc: "Lucien Dunning" <ldunning@...dia.com>,
Cc: "Cameron Buschardt" <cabuschardt@...dia.com>,
Cc: "Arvind Gopalakrishnan" <arvindg@...dia.com>,
Cc: "Haggai Eran" <haggaie@...lanox.com>,
Cc: "Or Gerlitz" <ogerlitz@...lanox.com>,
Cc: "Sagi Grimberg" <sagig@...lanox.com>
Cc: "Shachar Raindel" <raindel@...lanox.com>,
Cc: "Liran Liss" <liranl@...lanox.com>,
Cc: "Roland Dreier" <roland@...estorage.com>,
Cc: "Sander, Ben" <ben.sander@....com>,
Cc: "Stoner, Greg" <Greg.Stoner@....com>,
Cc: "Bridgman, John" <John.Bridgman@....com>,
Cc: "Mantor, Michael" <Michael.Mantor@....com>,
Cc: "Blinzer, Paul" <Paul.Blinzer@....com>,
Cc: "Morichetti, Laurent" <Laurent.Morichetti@....com>,
Cc: "Deucher, Alexander" <Alexander.Deucher@....com>,
Cc: "Leonid Shamis" <Leonid.Shamis@....com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists