Bug 840270 - qperf: the codes allow mtu_size to be 4K but failed when it came to practice
qperf: the codes allow mtu_size to be 4K but failed when it came to practice
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: qperf (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Doug Ledford
Infiniband QE
Depends On: 840269
  Show dependency treegraph
Reported: 2012-07-15 04:46 EDT by hali
Modified: 2013-03-07 19:09 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 840269
Last Closed: 2012-08-13 10:39:03 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description hali 2012-07-15 04:46:17 EDT
+++ This bug was initially created as a clone of Bug #840269 +++

Description of problem:
The qperf codes would check the mtu_size provided by user, and if it is exactly between 256/512/1K/2K/4K, it will try to modify qp with the specified mtu_size.

line 2006 of rdma.c of qperf-0.4.6:
error(0, "bad MTU: %d; must be 256/512/1K/2K/4K", mtu);

But actually, if the mtu_size is 4K, it will cause ib_modify_qp fail, and the reason is 'Invalid argument'

So if qperf support mtu_size 4K, it is supposed to be no failure. and if it does fail, please don't suppot it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.server side
[root@rdma3 qperf]# qperf

2. client side
[root@rdma2 qperf]# qperf 172.31.03 --mtu_size 2K uc_bw
    send_bw  =  974 MB/sec
    recv_bw  =    0 bytes/sec
[root@rdma2 qperf]# qperf 172.31.03 --mtu_size 4K uc_bw
failed to modify QP to RTR: Invalid argument
Comment 1 RHEL Product and Program Management 2012-08-07 04:49:02 EDT
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.
Comment 2 Doug Ledford 2012-08-13 10:39:03 EDT
This is not a bug.  qperf supports 4k MTUs just fine, however the MTU on the given device is limited to whatever the device and switch are set to.  So, even though qperf supports a 4k MTU, the 4k MTU can only be used if the physical MTU of the device is also set to 4k.  It is very common to have a device that is limited to a 2k MTU, and in that case qperf can only go up to using a 2k MTU.

Note You need to log in before you can comment on or make changes to this bug.