dat.conf (5) - Linux Manuals
dat.conf: configuration file for static registration of user-level DAT rdma providers
NAMEdat.conf - configuration file for static registration of user-level DAT rdma providers
The DAT (direct access transport) architecture supports the use of multiple DAT providers within a single consumer application. Consumers implicitly select a provider using the Interface Adapter name parameter passed to dat_ia_open().
The subsystem that maps Interface Adapter names to provider implementations is known as the DAT registry. When a consumer calls dat_ia_open(), the appropriate provider is found and notified of the consumer's request to access the IA. After this point, all DAT API calls acting on DAT objects are automatically directed to the appropriate provider entry points.
A persistent, administratively configurable database is used to store mappings from IA names to provider information. This provider information includes: the file system path to the provider library object, version information, and thread safety information. The location and format of the registry is platform dependent. This database is known as the Static Registry (SR) and is provided via entries in the dat.conf file. The process of adding a provider entry is termed Static Registration.
Registry File Formatacters after # on a line are ignored (comments).
and comments are considered blank lines and are ignored.
These fields may contain whitespace if the field is quoted
with double quotes. Within fields quoated with double quotes,
the backslash or qoute are valid escape sequences:
OpenFabrics RDMA providers:ovider options for both 1.2 and 2.0, each using different CM services