Isn't it enough that something like rsockets can run on a device to
justify its existence?
?? rsockets requires RC RDMA QPs, EFA won't support it.
I was referring to datagram rsockets...
Even so, I don't think EFA has an addressing model compatible with
rsockets, it doesn't use RDMA-CM either, which I think rsockets
requires still for UD??
I'd assume that EFA proprietary stuff matches IPv4/v6 to their
something so they can hook into ucma?
otherwise how would addressing work at all? Perhaps Gal can share
more on this...
Our addressing does not rely on rdmacm, also, there is no matching netdevice
(ipv4/6) for the EFA ib device.
I suppose one can be made though? even in SW implementing some sort of
indirection table?
Each EFA device has a 16 bytes opaque GID (queried from the device) that should
be specified when creating the AH.
libfabric's connection manager (out of band) is used to exchange these device
GIDs and destination QP numbers.
Does that answer your questions?
Yes, but I do tend to agree with the notion that efa needs to be made to
fit uverbs better. That means a libibverbs provider and a efacm
component that can map to rdma_ucm. Is that feasible?
