dat.conf man page on RedHat

Man page or keyword search:  
man Server   29550 pages
apropos Keyword Search (all sections)
Output format
RedHat logo
[printable version]

DAT.CONF(5)							   DAT.CONF(5)

NAME
       dat.conf - configuration file for static registration of user-level DAT
       rdma providers

DESCRIPTION
       The DAT (direct access transport) architecture supports the use of mul‐
       tiple  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 implementa‐
       tions  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 appropri‐
       ate provider entry points.

       A persistent, administratively configurable database is used  to	 store
       mappings	 from IA names to provider information. This provider informa‐
       tion 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 Registra‐
       tion.

Registry File Format

	   * All characters after # on a line are ignored (comments).
	   * Lines on which there are no characters other than whitespace
	     and comments are considered blank lines and are ignored.
	   * Non-blank lines must have seven whitespace separated fields.
	     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:
	   * Each non-blank line will contain the following fields:
	       - The IA Name.
	       - The API version of the library:
		 [k|u]major.minor where "major" and "minor" are both integers
		 in decimal format. User-level examples: "u1.2", and "u2.0".
	       -  Whether  the	library is thread-safe: [threadsafe|nonthread‐
       safe]
	       - Whether this is the default section: [default|nondefault]
	       - The library image, version included, to be loaded.
	       - The vendor id and version of DAPL provider: id.major.minor
	       - ia params, IA specific parameters - device name and port
	       - platform params, (not used)

OpenFabrics RDMA providers:

	   Provider options for both 1.2 and 2.0, each using different CM ser‐
       vices

	       1.  cma	-  OpenFabrics	rdma_cm	   - uses rdma_cm services for
       connections
					       - requires IPoIB and SA/SM ser‐
       vices for IB
					       -  netdev used for device name,
       without port designation (ia_params)
					       -   Supports   any    transport
       rdma_cm supports including IB, iWARP, RoCEE
					       -   libdaplcma.so  (1.2),  lib‐
       daplofa (2.0)

	       2. scm - uDAPL socket based CM  - exchanges CM information over
       sockets
					       -   eliminates	the  need  for
       rdma_cm, IPoIB, and SA for IB
					       - verbs device used for	device
       name with port designation (ia_param)
					       -  Supports  IB, RoCEE. Doesn't
       support iWARP
					       -  libdaplscm.so	 (1.2),	  lib‐
       daploscm (2.0)

	       3.  ucm - uDAPL unreliable IB CM - exchanges CM information via
       IB UD QP's
					       - eliminates the need for sock‐
       ets or rdma_cm
					       -  verbs device used for device
       name with port designation (ia_param)
					       - Supports  IB  only,  no  name
       service.
					       -   libdaplucm.so  (1.2),  lib‐
       daploucm (2.0)

Example entries for each OpenFabrics provider

	       1. cma - OpenFarbrics rdma_cm (v1.2 and v2.0 examples)

	       OpenIB-cma u1.2 nonthreadsafe default libdaplcma.so.1  dapl.1.2
       "ib0 0" ""
	       ofa-v2-ib0  u2.0 nonthreadsafe default libdaplofa.so.2 dapl.2.0
       "ib0 0" ""
	       ofa-v2-iwarp   u2.0   nonthreadsafe   default   libdaplofa.so.2
       dapl.2.0 "eth2 0" ""
	       ofa-v2-cma-roe-eth2  u2.0 nonthreadsafe default libdaplofa.so.2
       dapl.2.0 "eth2 0" ""
	       ofa-v2-cma-roe-eth3 u2.0 nonthreadsafe default  libdaplofa.so.2
       dapl.2.0 "eth3 0" ""

	       NOTE:  The OpenFabrics CMA providers use <ia_params> to specify
       the device with one of the following:
		     network address, network hostname, or netdev name;	 along
       with port number.

	       2. scm - uDAPL socket based CM (v1.2 and v2.0 examples)

	       OpenIB-mlx4_0-1	 u1.2  nonthreadsafe  default  libdaplscm.so.1
       dapl.1.2 "mlx4_0 1" ""
	       OpenIB-ipath0-1	u1.2  nonthreadsafe  default   libdaplscm.so.1
       dapl.1.2 "ipath0 1" ""
	       ofa-v2-mlx4_0-1	u2.0  nonthreadsafe  default  libdaploscm.so.2
       dapl.2.0 "mlx4_0 1" ""
	       ofa-v2-mlx4_0-2	u2.0  nonthreadsafe  default  libdaploscm.so.2
       dapl.2.0 "mlx4_0 2" ""
	       ofa-v2-mlx4_1-1	u2.0  nonthreadsafe  default  libdaploscm.so.2
       dapl.2.0 "mlx4_1 1" ""
	       ofa-v2-ehca0-1  u2.0  nonthreadsafe  default   libdaploscm.so.2
       dapl.2.0 "ehca0 1" ""
	       ofa-v2-scm-roe-mlx4_0-1	 u2.0	nonthreadsafe	default	  lib‐
       daploscm.so.2 dapl.2.0 "mlx4_0 1" ""

	       3. ucm - uDAPL unreliable IB CM	(not supported	in  1.2,  v2.0
       examples)

	       ofa-v2-mlx4_0-1u	 u2.0  nonthreadsafe  default libdaploucm.so.2
       dapl.2.0 "mlx4_0 1" ""
	       ofa-v2-mlx4_0-2u u2.0  nonthreadsafe  default  libdaploucm.so.2
       dapl.2.0 "mlx4_0 2" ""
	       ofa-v2-ipath0-1u	 u2.0  nonthreadsafe  default libdaploucm.so.2
       dapl.2.0 "ipath0 1" ""
	       ofa-v2-ehca0-1u	u2.0  nonthreadsafe  default  libdaploucm.so.2
       dapl.2.0 "ehca0 1" ""

	       Note:  OpenIB-  and  ofa-v2-  IA	 names	are  unique  mappings,
       reserved for OpenFabrics providers.

       The default location for this configuration file is /etc/dat.conf.

       The file location may  be  overridden  with  the	 environment  variable
       DAT_OVERRIDE=/your_own_directory/your_dat.conf.

SEE ALSO rdma_cm verbs socket
				 25 March 2008			   DAT.CONF(5)
[top]

List of man pages available for RedHat

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net