On Wed, Nov 23, 2016 at 02:42:12PM -0800, Dan Williams wrote:
> The crucial part for this discussion is the ability to fence and
> DMA for a specific range. This is the hardware capability that lets
> page migration happen: fence&block DMA, migrate page, update page
> table in HCA, unblock DMA.
Wait, ODP requires migratable pages, ZONE_DEVICE pages are not
Does it? I didn't think so.. Does ZONE_DEVICE break MMU notifiers/etc
or something? There is certainly nothing about the hardware that cares
about ZONE_DEVICE vs System memory.
I used 'migration' in the broader sense of doing any transformation to
the page such that the DMA address changes - not the specific kernel
You can't replace a PCIe mapping with just any other System RAM
physical address, right?
I thought that was exactly what HMM was trying to do? Migrate pages
between CPU and GPU memory as needed. As Serguei has said this process
needs to be driven by the GPU driver.
The peer-peer issue is how do you do that while RDMA is possible on
those pages, because when the page migrates to GPU memory you want the
RDMA to follow it seamlessly.
This is why page table mirroring is the best solution - use the
existing mm machinery to link the DMA driver and whatever is
controlling the VMA.
At least not without a filesystem recording where things went, but
at point we're no longer talking about the base P2P-DMA mapping
In the filesystem/DAX case, it would be the filesystem that initiates
any change in the page physical address.
ODP *follows* changes in the VMA it does not cause any change in
address mapping. That has to be done by whoever is in charge of the
something like pnfs-rdma to a DAX filesystem.
Something in the kernel (ie nfs-rdma) would be entirely different. We
generally don't do long lived mappings in the kernel for RDMA
(certainly not for NFS), so it is much more like your basic every day
DMA operation: map, execute, unmap. We probably don't need to use page
table mirroring for this.
ODP comes in when userpsace mmaps a DAX file and then tries to use it
for RDMA. Page table mirroring lets the DAX filesystem decide to move
the backing pages at any time. When it wants to do that it interacts
with the MM in the usual way which links to ODP and makes sure the
migration is seamless.