[libfabric-users] mmap'ed kernel memory in fi_mr_reg
sean.hefty at intel.com
Fri Nov 16 08:35:38 PST 2018
> I am happy with this being a provider-specific extension for now. The
> project that requires this will anyway only use the verbs provider.
> I do not think there is a fully reliable way of distinguishing
> physical/virtual addresses. I spoke with our driver expert here who
> cannot think of a way either. The provider-specific flag seems to be
> the way to go, what do you think?
I agree this works fine.
The only alternative I can think of is to try a normal registration call, and if that fails, try again using the physical flag. Would this work, or does the normal registration call succeed, but produce an unusable MR?
More information about the Libfabric-users