tavor(7d) [opensolaris man page]
tavor(7D) tavor(7D) NAME
tavor - InfiniHost MT23108/MT25208 InfiniBand (IB) Driver SYNOPSIS
PCI pci15b3,5a44@pci-slot, pci15b3,5a45@pci-slot PCI-E pci15b3,6278@pci-e-slot, pci15b3,6279@pci-e-slot The tavor driver is an IB Architecture-compliant implementation of an HCA, which operates on the Mellanox MT23108 InfiniBand ASSP and the Mellanox MT25208 InfiniBand ASSP. These ASSP's support the link and physical layers of the InfiniBand specification, while the ASSP and the driver support the transport layer. The tavor driver interfaces with the InfiniBand Transport Framework (IBTF) and provides an implementation of the Channel Interfaces that are defined by that framework. It also enables management applications and agents to access the IB fabric. FILES
/kernel/drv/tavor 32-bit ELF kernel module ( platform only). /kernel/drv/amd64/tavor 64-bit ELF kernel module ( platform only). /kernel/drv/sparcv9/tavor 64-bit ELF Kernel Module (SPARC platform only). /kernel/drv/tavor.conf Driver configuration file. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |PCI-based systems | +-----------------------------+-----------------------------+ |Availability |SUNWtavor | +-----------------------------+-----------------------------+ driver.conf(4), printers.conf(4), attributes(5) Writing Device Drivers In addition to being logged, the following messages may appear on the system console. tavor : driver attached for maintenance mode only. There was a failure in the boot process of the tavor ASSP and the only function that can be performed is to re-flash firmware on the ASSP. driver failed to attach. The ASSP could not boot into either operational (HCA) mode or into maintenance mode. The device in inoperable. Unexpected port number in port state change event. A port state change event occurred, but the port number in the message does not exist on this HCA. This message also indicates the port number that was in the port state change. Tavor driver successfully detached. The driver has been removed from the system, and the HCA is no longer available for transfer operations. tavor"n": port "m" up. A port up asynchronous event has occured. "n" represents the instance of the Tavor device number, and "m" represents the port number on the Tavor device. tavor"n": port "m" down. A port down aynchronous event has occurred. Tavor: <command name> command failed. A internal firmware command failed to execute. 11 Feb 2005 tavor(7D)
Check Out this Related Man Page
service_provider.conf(4) File Formats service_provider.conf(4) NAME
service_provider.conf - service provider configuration file SYNOPSIS
service_provider.conf DESCRIPTION
service_provider.conf contains information about the device type that the service provider supports. This information includes the pathname of the service provider library, the library version and other library characteristics that are required by the system administrative com- mand, datadm(1M). datadm(1M) puts this information in the DAT static register file, dat.conf(4). The datadm program enumerates each device entry into a list of interface adapters, that is, interfaces to external network that are avail- able to uDAPL consumers. This new list of interface adapters is appended to other service providers' information in the DAT static reg- istry, dat.conf. You can do this is you invoke the datadm program with the -a option and the pathname of the service_provider.conf file. Each entry in the service_provider.conf is a single line of 7 fields. The following shows the order of the fields in a service_provider.conf entry: "driver_name" "API_version" "threadsafe_library | nonthreadsafe_library" "default_version | nondefault_version" "service_provider_library_pathname" "service_provider_version" "service_provider_instance_data" The fields are defined as follows: driver_name Specifies a driver name in the format of driver_name=value pair, for example, driver_name=tavor. API_version Specifies the API version of the service provide library: For example, "u"major.minor is u1.2. threadsafe_library | nonthreadsafe_librar Specifies a threadsafe or non-threadsafe library. default_version | nondefault_version Specifies a default or non-default version of library. A service provider can offer several versions of the library. If so, one version is designated as default with the rest as nondefault. service_provider_library_pathname Specifies the pathname of the library image. service_provider_version Specifies the version of the service provider. By convention, specify the company stock symbol as the service provider, followed by major and minor version numbers, for example, SUNW1.0. service_provider_instance_data Specifies the service provider instance data. EXAMPLES
Example 1 Using a Logical Device Name The following example service_provider.conf entry uses a logical device name: # # Sample service_provider.conf entry showing an uDAPL 1.2 service # provider, udapl_tavor.so.1 supporting a device with a driver named # tavor driver_name=tavor u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 "" Example 2 Using a Physical Device Name The following example service_provider.conf uses a physical device name: # # Sample service_provider.conf entry showing an uDAPL 1.2 # service provider, udapl_tavor.so.1 supporting a device named # pci15b3,5a44 that can be located under /devices # pci15b3,5a44 u1.2 nonthreadsafe default /usr/lib/tavor/udapl_tavor.so.1 SUNWudaplt1.0 "" ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
datadm(1M), dat.conf(4), attributes(5) SunOS 5.11 18 Jun 2004 service_provider.conf(4)