> > 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? Not quite - this isn't running a connection protocol. The closest in tree comparison would be the IB SIDR protocol used in conjunction with IP addresses. I’m not aware of anyone using that, however. Unconnected endpoints typically have an existing out of band mechanism (e.g. PMI) that can be used for address exchange. The PSM/2 drivers make a similar assumption. - Sean
