public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liu, Changcheng" <changcheng.liu@intel.com>
To: linux-rdma@vger.kernel.org
Subject: Re: qperf failure
Date: Wed, 30 Oct 2019 15:09:13 +0800	[thread overview]
Message-ID: <20191030070913.GA1901339@jerryopenix> (raw)
In-Reply-To: <20191028032728.GA1026409@jerryopenix>

Does anyone use qperf to compare TCP & RDMA-RC-Send/Recv bandwidth and latency?

On 11:27 Mon 28 Oct, Liu, Changcheng wrote:
> Hi all,
>    I'm using qperf to compare TCP & RDMARC performance.
>    qperf report that it failed to modify the QP to RTR status.
>    Does anyone know how to solve the problem?
> 
>    Host A:nstcloudcc1 configuration:
>        nstcc1@nstcloudcc1:tmp$ ib2netdev 
>        mlx5_0 port 1 ==> ens261f0 (Up) 173.168.100.103
>        mlx5_1 port 1 ==> ens261f1 (Down) 
>        nstcc1@nstcloudcc1:tmp$ 
>    Host B:rdmarhel0 configuration:
>        [rdma@rdmarhel0 tmp]$ ib2netdev 
>        mlx5_0 port 1 ==> ens801f0 (Up) 173.168.100.101
>        mlx5_1 port 1 ==> ens801f1 (Up) 192.168.100.101
>        [rdma@rdmarhel0 tmp]$ 
> 
>    Run below command on host A as server:
>        nstcc1@nstcloudcc1:tmp$ qperf
>    Run below command on host B as client:
>        [rdma@rdmarhel0 tmp]$ qperf 173.168.100.103 rc_bw
>        rc_bw:
>        failed to modify QP to RTR: Invalid argument
>    The log shows as above on cient that it failed to modify QP to RTR
> 
> --Thanks
> Changcheng

      reply	other threads:[~2019-10-30  7:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28  3:27 qperf failure Liu, Changcheng
2019-10-30  7:09 ` Liu, Changcheng [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191030070913.GA1901339@jerryopenix \
    --to=changcheng.liu@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox