On 28/11/16 12:35 PM, Serguei Sagalovitch wrote:I assume that you are talking about "invalidate_peer_memory()' callback?
As soon as PeerDirect mapping is called then GPU must not "move" theWe haven't touch this in a long time and perhaps it changed, but there
such memory. It is by PeerDirect design. It is similar how it is works
with system memory and RDMA MR: when "get_user_pages" is called then the
memory is pinned.
definitely was a call back in the PeerDirect API to allow the GPU to
invalidate the mapping. That's what we don't want.