On 1/4/19 5:09 PM, Hefty, Sean wrote:
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?
EFA supports connectionless communication. Mapping to rdma_ucm doesn't make
sense to me.
Gal said that address libfabric connection manager is used to resolve
addressing... so there is some connection manager involved...
I haven't see the libfabric provider yet, but libfabric has generic out-of-band socket-based name service that can be used by provider > I'm guessing that's what Gal is referring to. The name service is
primarily there to support fabtests.
In realistic use cases, those providers rely on a job manager to exchange addressing, with name service support disabled.
I think that this is what I was referring to by introducing efacm like
ibcm and iwcm... Isn't it in essence the same thing?
