9–iWARP Configuration
Configuring iWARP on Linux
130
AH0054602-00 A
2.
On one client, issue the following command:
[root@localhost ~]#
ib_send_bw -d qedr1 -F -R 192.168.11.3
----------------------------------------------------------------------------
Send BW Test
Dual-port : OFF Device : qedr1
Number of qps : 1 Transport type : IW
Connection type : RC Using SRQ : OFF
TX depth : 128
CQ Moderation : 100
Mtu : 1024[B]
Link type : Ethernet
GID index : 0
Max inline data : 0[B]
rdma_cm QPs : ON
Data ex. method : rdma_cm
----------------------------------------------------------------------------
local address: LID 0000 QPN 0x0192 PSN 0xcde932
GID: 00:14:30:196:192:110:00:00:00:00:00:00:00:00:00:00
remote address: LID 0000 QPN 0x0098 PSN 0x46fffc
GID: 00:14:30:196:195:62:00:00:00:00:00:00:00:00:00:00
----------------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec] MsgRate[Mpps]
65536 1000 2250.38 2250.36 0.036006
----------------------------------------------------------------------------
Using iSER with iWARP
Configure the iSER initiator and target similar to RoCE to work with iWARP. You
can use different methods to create a Linux-IO Target (LIO
™
); one is listed in this
section. You may encounter some difference in targetcli configuration in SLES 12
and RHEL 7.
x
because of the version.
NOTE
For latency applications (send/write), if the perftest version is the latest (for
example,
perftest-3.0-0.21.g21dc344.x86_64.rpm
), use the
supported inline size value:
0-128
.
