1. Who should use the TCP/IP driver

Version 4.4.0 and newer of the Dolphin software stack includes a legacy TCP/IP driver (IPoPCIe) for the PCI Express interconnect. Most applications should NOT use this driver as SuperSockets normally will give much lower latency and higher throughput. However, some applications and services are not supported by SuperSockets and needs to use the TCP/IP driver to benefit from PCI Express. The following applications are known to benefit from the TCP/IP driver:

1.1. Enable Linux applications to use the Dolphin PCI Express TCP/IP driver

This section explains how to use the Dolphin PCI Express TCP/IP (IPoPCIe) driver.

The IPoPCIe driver is part of the SuperSockets driver and require that SuperSockets has been enabled and properly configured. Please refer to separate installation/configuration descriptions for SuperSockets in this document.

Assuming SuperSockets is properly configured you should have a 'dis0' network interface available: .

# ifconfig dis0 
dis0      Link encap:Ethernet HWaddr 00:00:00:00:00:00 
          NOARP MTU:9000 Metric:1 
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
	         collisions:0 txqueuelen:1000 
	         RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) 

To use the adapter you have to configure it with an IP address. You may use any valid IP address.

The dis0-interface supports the common ifconfig configuration parameters like this:

# ifconfig dis0 netmask (example)

Repeat this for all Cluster Nodes which you want to communicate with using IPoPCIe.

You can verify connectivity by using ping against remote Cluster Nodes:

# ping

IPoPCIe should now be ready to be used.