fi_provider man page

Fabric Interface Providers


Conceptually, a fabric provider may be viewed as a local hardware NIC driver, though a provider is not limited by this definition. The first component of libfabric is a general purpose framework that is capable of handling different types of fabric hardware. All fabric hardware devices and their software drivers are required to support this framework. Devices and the drivers that plug into the libfabric framework are referred to as fabric providers, or simply providers.

This distribution of libfabric contains the following providers (although more may be available via run-time plug-ins):

GNI : A provider for the Aries interconnect in Cray XC(TM) systems utilizing the user-space Generic Networking Interface. See fi_gni(7) for more information.

PSM : High-speed InfiniBand networking from Intel. See fi_psm(7) for more information.

Sockets : A general purpose provider that can be used on any network that supports TCP/UDP sockets. This provider is not intended to provide performance improvements over regular TCP/UDP sockets, but rather to allow developers to write, test, and debug application code even on platforms that do not have high-speed networking. See fi_sockets(7) for more information.

usNIC : Ultra low latency Ethernet networking over Cisco userspace VIC adapters. See fi_usnic(7) for more information.

Verbs : This provider uses the Linux Verbs API for network transport. Application performance is, obviously expected to be similar to that of the native Linux Verbs API. Analogous to the Sockets provider, the Verbs provider is intended to enable developers to write, test, and debug application code on platforms that only have Linux Verbs-based networking. See fi_verbs(7) for more information.

Provider Requirements

Libfabric provides a general framework for supporting multiple types of fabric objects and their related interfaces. Fabric providers have a large amount of flexibility in selecting which components they are able and willing to support, based on specific hardware constraints. Provider developers should refer to docs/provider for information on functionaliy supplied by the framework to assist in provider implementation. To assist in the development of applications, libfabric specifies the following requirements that must be met by any fabric provider, if requested by an application.

Note that the instantiation of a specific fabric object is subject to application configuration parameters and need not meet these requirements.

Future versions of libfabric will automatically enable a more complete set of features for providers that focus their implementation on a narrow subset of libfabric capabilities.

Logging Interface

Logging is performed using the FI_ERR, FI_LOG, and FI_DEBUG macros.


#define FI_ERR(prov_name, subsystem, ...)

#define FI_LOG(prov_name, prov, level, subsystem, ...)

#define FI_DEBUG(prov_name, subsystem, ...)


prov_name : String representing the provider name.

prov : Provider context structure.

level : Log level associated with log statement.

subsystem : Subsystem being logged from.


FI_ERR : Always logged.

FI_LOG : Logged if the intended provider, log level, and subsystem parameters match the user supplied values.

FI_DEBUG : Logged if configured with the --enable-debug flag.

See Also

fi_gni(7), fi_psm(7), fi_sockets(7), fi_usnic(7), fi_verbs(7),



Referenced By

fabric(7), fi_psm(7), fi_psm2(7), fi_sockets(7), fi_udp(7), fi_usnic(7), fi_verbs(7).

2016-02-28 Libfabric Programmer's Manual Libfabric v1.4.1