fi_udp(7)

🎀 NAME 🎀

okay so fi_udp(7) is the manual for The UDP Fabric Provider — that’s the whole name, bestie 💅

🌈 OVERVIEW 🌈

The UDP provider is a basic provider that works on any system that supports UDP sockets. It is not intended to provide performance improvements over regular TCP sockets, no cap — instead, it’s there to allow application and provider developers to write, test, and debug their code. 🫶

It also forms the foundation of a utility provider that enables the implementation of libfabric features over any hardware. iconic behavior, honestly. ✨

✨ SUPPORTED FEATURES ✨

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

Endpoint types

• The provider supports only endpoint type FI_EP_DGRAM. periodt.

Endpoint capabilities

• The following data transfer interface is supported: fi_msg.
• The provider supports standard unicast datagram transfers, as well as multicast operations. 🎀

Modes

• The provider does not require the use of any mode bits. none. zero. zilch. ✨

Progress

• The UDP provider supports both FI_PROGRESS_AUTO and FI_PROGRESS_MANUAL, with a default set to auto.
• Important caveat: receive side data buffers are not modified outside of completion processing routines. 🫶

💀 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. no cap, they’re fixed.
• EPs must be bound to both RX and TX CQs.
• No support for selective completions or multi-recv.
• No support for counters.

🧚 RUNTIME PARAMETERS 🧚

No runtime parameters are currently defined. literally none rn 🙈

🌸 SEE ALSO 🌸

• fabric(7)
• fi_provider(7)
• fi_getinfo(3)

👑 AUTHORS 👑

OpenFabrics. 💜

---

xoxo, this page is from the Libfabric Programmer’s Manual, Libfabric v2.5.1, dated 2024-12-10 — go slay your UDP situation, bestie 💖🫶✨