[ofiwg] completion flags as actually defined by OFI
Hefty, Sean
sean.hefty at intel.com
Thu Apr 16 13:31:25 PDT 2015
These are the new completion flags and their definitions that I have in a pending patch.
*FI_INJECT_COMPLETE*
: Indicates that a completion should be generated when the
source buffer(s) may be reused. A completion guarantees that
the buffers will not be read from again and the application may
reclaim them. No other guarantees are made with respect to the
state of the operation.
*FI_TRANSMIT_COMPLETE*
: Indicates that a completion should be generated when the transmit
operation has completed relative to the local provider. The exact
behavior is dependent on the endpoint type.
For reliable endpoints:
Indicates that a completion should be generated when the operation has
been delivered to the peer endpoint. A completion guarantees that the
operation is no longer dependent on the fabric or local resources. The
state of the operation at the peer endpoint is not defined.
For unreliable endpoints:
Indicates that a completion should be generated when the operation has
been delivered to the fabric. A completion guarantees that the
operation is no longer dependent on local resources. The state of the
operation within the fabric is not defined.
*FI_DELIVERY_COMPLETE*
: Indicates that a completion should not be generated until an operation
has been processed by the destination endpoint(s). A completion
guarantees that the targets have visibility into the results of the operation.
This completion mode applies only to reliable endpoints. For operations
that return data to the initiator, such as RMA read or atomic-fetch,
the source endpoint is also considered a destination endpoint. This is the
default completion mode for such operations.
More information about the ofiwg
mailing list