On Mon, Nov 28, 2016 at 04:55:23PM -0500, Serguei Sagalovitch wrote: > >We haven't touch this in a long time and perhaps it changed, but there > >definitely was a call back in the PeerDirect API to allow the GPU to > >invalidate the mapping. That's what we don't want. > I assume that you are talking about "invalidate_peer_memory()' callback? > I was told that it is the "last resort" because HCA (and driver) is not > able to handle it in the safe manner so it is basically "abort" everything. If it is a last resort to save system stability then kill the impacted process, that will release the MRs. Jason _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
