logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

fi_udp - The UDP Fabric Provider

Authors

       OpenFabrics.

Libfabric Programmer’s Manual                      2024-12-10                                          fi_udp(7)

Limitations

       The  UDP provider has hard-coded maximums for supported queue sizes and data transfers.  These values are
       reflected in the related fabric attribute structures

       EPs must be bound to both RX and TX CQs.

       No support for selective completions or multi-recv.

       No support for counters.

Name

       fi_udp - The UDP Fabric Provider

Overview

       The  UDP  provider  is  a  basic  provider that can be used on any system that supports UDP sockets.  The
       provider is not intended to provide performance improvements over regular TCP sockets, but rather to  al‐
       low application and provider developers to write, test, and debug their code.  The UDP provider forms the
       foundation of a utility provider that enables the implementation of libfabric features over any hardware.

Runtime Parameters

       No runtime parameters are currently defined.

See Also

fabric(7), fi_provider(7), fi_getinfo(3)

Supported Features

       The  UDP  provider  supports a minimal set of features useful for sending and receiving datagram messages
       over an unreliable endpoint.

       Endpointtypes
              The provider supports only endpoint type FI_EP_DGRAM.

       Endpointcapabilities
              The following data transfer interface is supported: fi_msg.  The provider supports  standard  uni‐
              cast datagram transfers, as well as multicast operations.

       Modes  The provider does not require the use of any mode bits.

       Progress
              The  UDP provider supports both FI_PROGRESS_AUTO and FI_PROGRESS_MANUAL, with a default set to au‐
              to.  However, receive side data buffers are not modified outside  of  completion  processing  rou‐
              tines.

See Also