All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yanjun Zhu <yanjun.zhu@linux.dev>
To: Alexander Kalentyev <comrad.karlovich@gmail.com>,
	linux-rdma@vger.kernel.org
Subject: Re: rdma_rxe usage problem
Date: Wed, 19 Jan 2022 22:12:51 +0800	[thread overview]
Message-ID: <d6551275-6d84-d117-dfa3-91956860ab05@linux.dev> (raw)
In-Reply-To: <CABrV9Yt0HYenR_qk_QWFkvH4-0Ooeb61y+CyT3WVOnDiAmxjhA@mail.gmail.com>

在 2022/1/19 19:42, Alexander Kalentyev 写道:
> I am trying to install and use soft RoCE for development purposes
> (right now on a localhost).
> I installed rdma-core on a MANJARO system from AUR.
> Then I did:
> 
> sudo modprobe rdma_rxe
> sudo rdma link add rxe0 type rxe netdev wlp60s0
> 
> then ibstat shows:
> CA 'rxe0'
>          CA type:
>          Number of ports: 1
>          Firmware version:
>          Hardware version:
>          Node GUID: 0x4a51c5fffef6e159
>          System image GUID: 0x4a51c5fffef6e159
>          Port 1:
>                  State: Active
>                  Physical state: LinkUp
>                  Rate: 2.5
>                  Base lid: 0
>                  LMC: 0
>                  SM lid: 0
>                  Capability mask: 0x00010000
>                  Port GUID: 0x4a51c5fffef6e159
>                  Link layer: Ethernet

Can rping work after you configured this test environment?

Zhu Yanjun

> 
> But launching any example I always get an error by call of: ibv_modify_qp
> with an attempt to modify QP state to RTR (for example by launching
> .ibv_rc_pingpong)
> The type of the error is EINVAL.
> I believe I miss something very obvious.


  reply	other threads:[~2022-01-19 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 11:42 rdma_rxe usage problem Alexander Kalentyev
2022-01-19 14:12 ` Yanjun Zhu [this message]
2022-01-19 17:53   ` Alexander Kalentyev
2022-01-19 19:54     ` Pearson, Robert B
2022-01-20 11:32       ` Alexander Kalentyev
2022-01-20 12:23         ` Leon Romanovsky
2022-01-20 13:21     ` Yanjun Zhu

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=d6551275-6d84-d117-dfa3-91956860ab05@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=comrad.karlovich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.