Your company here — click to reach over 10,000 unique daily visitors

fi_trigger - Man Page

Triggered operations


#include <rdma/fi_trigger.h>


Triggered operations allow an application to queue a data transfer request that is deferred until a specified condition is met. A typical use is to send a message only after receiving all input data. Triggered operations can help reduce the latency needed to initiate a transfer by removing the need to return control back to an application prior to the data transfer starting.

An endpoint must be created with the FI_TRIGGER capability in order for triggered operations to be specified. A triggered operation is requested by specifying the FI_TRIGGER flag as part of the operation. Such an endpoint is referred to as a trigger-able endpoint.

Any data transfer operation is potentially trigger-able, subject to provider constraints. Trigger-able endpoints are initialized such that only those interfaces supported by the provider which are trigger-able are available.

Triggered operations require that applications use struct fi_triggered_context as their per operation context parameter, or if the provider requires the FI_CONTEXT2 mode, struct fi_trigger_context2. The use of struct fi_triggered_context[2] replaces struct fi_context[2], if required by the provider. Although struct fi_triggered_context[2] is not opaque to the application, the contents of the structure may be modified by the provider once it has been submitted as an operation. This structure has similar requirements as struct fi_context[2]. It must be allocated by the application and remain valid until the corresponding operation completes or is successfully canceled.

Struct fi_triggered_context[2] is used to specify the condition that must be met before the triggered data transfer is initiated. If the condition is met when the request is made, then the data transfer may be initiated immediately. The format of struct fi_triggered_context[2] is described below.

struct fi_triggered_context {
    enum fi_trigger_event event_type;   /* trigger type */
    union {
        struct fi_trigger_threshold threshold;
        struct fi_trigger_xpu xpu;
        void *internal[3]; /* reserved */
    } trigger;

struct fi_triggered_context2 {
    enum fi_trigger_event event_type;   /* trigger type */
    union {
        struct fi_trigger_threshold threshold;
        struct fi_trigger_xpu xpu;
        void *internal[7]; /* reserved */
    } trigger;

The triggered context indicates the type of event assigned to the trigger, along with a union of trigger details that is based on the event type.

Completion Based Triggers

Completion based triggers defer a data transfer until one or more related data transfers complete. For example, a send operation may be deferred until a receive operation completes, indicating that the data to be transferred is now available.

The following trigger event related to completion based transfers is defined.


This indicates that the data transfer operation will be deferred until an event counter crosses an application specified threshold value. The threshold is specified using struct fi_trigger_threshold:

struct fi_trigger_threshold {
    struct fid_cntr *cntr; /* event counter to check */
    size_t threshold;      /* threshold value */

Threshold operations are triggered in the order of the threshold values. This is true even if the counter increments by a value greater than 1. If two triggered operations have the same threshold, they will be triggered in the order in which they were submitted to the endpoint.

Deferred Work Queues

The following feature and description are enhancements to triggered operation support.

The deferred work queue interface is designed as primitive constructs that can be used to implement application-level collective operations. They are a more advanced form of triggered operation. They allow an application to queue operations to a deferred work queue that is associated with the domain. Note that the deferred work queue is a conceptual construct, rather than an implementation requirement. Deferred work requests consist of three main components: an event or condition that must first be met, an operation to perform, and a completion notification.

Because deferred work requests are posted directly to the domain, they can support a broader set of conditions and operations. Deferred work requests are submitted using struct fi_deferred_work. That structure, along with the corresponding operation structures (referenced through the op union) used to describe the work must remain valid until the operation completes or is canceled. The format of the deferred work request is as follows:

struct fi_deferred_work {
    struct fi_context2    context;

    uint64_t              threshold;
    struct fid_cntr       *triggering_cntr;
    struct fid_cntr       *completion_cntr;

    enum fi_trigger_op    op_type;

    union {
        struct fi_op_msg            *msg;
        struct fi_op_tagged         *tagged;
        struct fi_op_rma            *rma;
        struct fi_op_atomic         *atomic;
        struct fi_op_fetch_atomic   *fetch_atomic;
        struct fi_op_compare_atomic *compare_atomic;
        struct fi_op_cntr           *cntr;
    } op;

Once a work request has been posted to the deferred work queue, it will remain on the queue until the triggering counter (success plus error counter values) has reached the indicated threshold. If the triggering condition has already been met at the time the work request is queued, the operation will be initiated immediately.

On the completion of a deferred data transfer, the specified completion counter will be incremented by one. Note that deferred counter operations do not update the completion counter; only the counter specified through the fi_op_cntr is modified. The completion_cntr field must be NULL for counter operations.

Because deferred work targets support of collective communication operations, posted work requests do not generate any completions at the endpoint by default. For example, completed operations are not written to the EP’s completion queue or update the EP counter (unless the EP counter is explicitly referenced as the completion_cntr). An application may request EP completions by specifying the FI_COMPLETION flag as part of the operation.

It is the responsibility of the application to detect and handle situations that occur which could result in a deferred work request’s condition not being met. For example, if a work request is dependent upon the successful completion of a data transfer operation, which fails, then the application must cancel the work request.

To submit a deferred work request, applications should use the domain’s fi_control function with command FI_QUEUE_WORK and struct fi_deferred_work as the fi_control arg parameter. To cancel a deferred work request, use fi_control with command FI_CANCEL_WORK and the corresponding struct fi_deferred_work to cancel. The fi_control command FI_FLUSH_WORK will cancel all queued work requests. FI_FLUSH_WORK may be used to flush all work queued to the domain, or may be used to cancel all requests waiting on a specific triggering_cntr.

Deferred work requests are not acted upon by the provider until the associated event has occurred; although, certain validation checks may still occur when a request is submitted. Referenced data buffers are not read or otherwise accessed. But the provider may validate fabric objects, such as endpoints and counters, and that input parameters fall within supported ranges. If a specific request is not supported by the provider, it will fail the operation with -FI_ENOSYS.

See Also

fi_getinfo(3), fi_endpoint(3), fi_mr(3), fi_alias(3), fi_cntr(3)



Referenced By


2024-03-07 Libfabric Programmer’s Manual Libfabric v1.21.0