8–iWARP Configuration
Configuring iWARP on Linux
173
AH0054602-00 J
2.
Issue the
ibv_devinfo
command, and then verify the transport type.
If the command is successful, each PCI function will show a separate
hca_id
. For example (if checking the second port of the above dual-port
adapter):
[root@localhost ~]#
ibv_devinfo -d qedr1
hca_id: qedr1
transport: iWARP (1)
fw_ver: 8.14.7.0
node_guid: 020e:1eff:fec4:c06e
sys_image_guid: 020e:1eff:fec4:c06e
vendor_id: 0x1077
vendor_part_id: 5718
hw_ver: 0x0
phys_port_cnt: 1
port: 1
state: PORT_ACTIVE (4)
max_mtu: 4096 (5)
active_mtu: 1024 (3)
sm_lid: 0
port_lid: 0
port_lmc: 0x00
link_layer: Ethernet
Supported iWARP Applications
Linux-supported RDMA applications for iWARP include the following:
ibv_devinfo, ib_devices
ib_send_bw/lat, ib_write_bw/lat, ib_read_bw/lat, ib_atomic_bw/lat
For iWARP, all applications must use the RDMA communication manager
(rdma_cm) using the
-R
option.
rdma_server, rdma_client
rdma_xserver, rdma_xclient
rping
NFS over RDMA (NFSoRDMA)
iSER (for details, see
NVMe-oF (for details, see