On 11/28/2018 09:51 PM, Hefty, Sean wrote:
RxM creates the underlying connection only when the first transfer
is attempted to a given peer. You will see EAGAIN until the
connection completes.
That makes sense. I guess there is no way to get notified of the
connection via an event?
An event is delivered to the RxM provider, but that is not exposed. This is an
implementation detail of how rxm works in conjunction with a MSG provider. Not
all RDM providers would have a similar restriction. More native ones probably
wouldn't.
Off the top of my head, I'm not sure what a good solution would be for avoiding
the first message setup latency, particularly one that wouldn't make things
worse on the app.
Thanks Sean. Couldn't the connection be established already when
inserting the remote address to the AV? From the API it looks like an
event can be generated once the insertion completes. In case of rxm this
could be when the connection is established.
Anyway, I can work around the EAGAIN in my application, so not a big
problem.
Cheers,
Jörn
_______________________________________________
ofiwg mailing list
[email protected]
https://lists.openfabrics.org/mailman/listinfo/ofiwg
