On 2016-11-27 09:02 AM, Haggai Eran wrote
On PeerDirect, we have some kind of a middle-ground solution for
GPU memory. We create a non-ODP MR pointing to VRAM but rely on
user-space and the GPU not to migrate it. If they do, the MR gets
destroyed immediately. This should work on legacy devices without ODP
support, and allows the system to safely terminate a process that
misbehaves. The downside of course is that it cannot transparently
migrate memory but I think for user-space RDMA doing that transparently
requires hardware support for paging, via something like HMM.
May be I am wrong but my understanding is that PeerDirect logic basically
follow "RDMA register MR" logic so basically nothing prevent to
process for "MMU notifier" case when we are very low on memory
not making it similar (not worse) then PeerDirect case.
> I'm hearing most people say ZONE_DEVICE is the way to handle
> which means the missing remaing piece for RDMA is some kind of DMA
> core support for p2p address translation..
Yes, this is definitely something we need. I think Will Davis's patches
are a good start.
Another thing I think is that while HMM is good for user-space
applications, for kernel p2p use there is no need for that.
About HMM: I do not
think that in the current form HMM would fit in
requirement for generic P2P transfer case. My understanding is that at
the current stage HMM is good for "caching" system memory
in device memory for fast GPU access but in RDMA MR non-ODP case
it will not work because the location of memory should not be
changed so memory should be allocated directly in PCIe memory.
Using ZONE_DEVICE with or without something like DMA-BUF to pin and
pages for the short duration as you wrote above could work fine for
kernel uses in which we can guarantee they are short.
Potentially there is another
issue related to pin/unpin. If memory could
be used a lot of time then there is no sense to rebuild and program
s/g tables each time if location of memory was not changed.