Chelsio Communications Terminator Series Installation And User Manual page 113

Chapter VI. WD-UDP
Routed through the Terminator acceleration device. If the ingress datagram arrives via a
device other than the Terminator acceleration device, then it will not utilize the acceleration
path. On egress, if the destination IP address will not route out via the Terminator device, then
it too will not be accelerated.
Using libcxgb4_sock
The libcxgb4_sock library utilizes the Linux RDMA Verbs subsystem, and thus requires the RDMA
modules be loaded. Ensure that your systems load the iw_cxgb4 and rdma_ucm modules:
[root@host~]# modprobe iw_cxgb4
[root@host~]# modprobe rdma_ucm
Now, preload libcxgb4_sock, using one of the methods mentioned below when starting your
application:
• Preloading using wdload script:
[root@host~]# PROT=UDP wdload <pathto>/your_application
The above command will generate an end point file, libcxgb4_sock.conf at /etc/. Parameters
like interface name and port number can be changed in this file.
The following example shows how to run Netperf with WD-UDP:
server:
[root@host~]# PROT=UDP wdload netserver -f -p <port_num>
client:
[root@host~]# PROT=UDP wdload netperf -H <hostIp> -p <port_num> -t UDP_RR
• Preloading manually
Create a configuration file that defines which UDP endpoints should be accelerated, their vlan
and priority if any, as well as which Terminator interface/port should be used. The file
/etc/libcxgb4_sock.conf
using libcxgb4_sock. Here is the syntax:
Chelsio Unified Wire for Linux
contains these endpoint entries. Create this file on all systems
113