Re: [ofiwg] [libfabric-users] Two-stage completion

2016-09-15 Thread Hefty, Sean
> And then what completion mode should I select? FI_DELIVERY_COMPLETE? I would let the provider select this. FI_DELIVERY_COMPLETE can have significant overhead based on the provider implementation. ___ ofiwg mailing list ofiwg@lists.openfabrics.org

Re: [ofiwg] [libfabric-users] Two-stage completion

2016-09-15 Thread Hefty, Sean
> If I start using the inject call to block until the buffer is safe, how > do I get the kind of completion I'd need for my timeout, if there's no > flags argument in the fi_tinject call? To reuse the buffer immediately but still get a completion, you should call fi_tsendmsg with the FI_INJECT

Re: [ofiwg] [libfabric-users] Two-stage completion

2016-09-15 Thread Hefty, Sean
> You looking at the flags discussion for the send/receive operations. You -> you're > This is calling out that those flags only apply to the fi_sendmsg call. > Other send operations do no take flags, and they do not apply to the No -> not Apparently I need more sleep.

Re: [ofiwg] [libfabric-users] Two-stage completion

2016-09-15 Thread Hefty, Sean
> ...oh? I thought that FI_TRANSMIT_COMPLETE was the local completion and > FI_DELIVERY_COMPLETE was the remote completion. What does this mean, > then? > > FI_TRANSMIT_COMPLETE > Applies to fi_sendmsg. Indicates that a completion should not be > generated until the operation has been