From: Marcin Mielniczuk <marcin@golem.network>
To: Leon Romanovsky <leon@kernel.org>,
Krishnamraju Eraparaju <krishna2@chelsio.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: Setting up siw devices
Date: Fri, 23 Aug 2019 16:17:50 +0200 [thread overview]
Message-ID: <945643c8-198e-f8bf-1e8f-536f77612db0@golem.network> (raw)
In-Reply-To: <b4bf4bc2-8dc7-a2c2-6bd2-ab41d9fbadc9@golem.network>
While the device is detected by ibv_devices and rping works, I can't get
ibv_rc_pingpong working
(and as far as I understand, RC should be supported by the iWARP driver)
rping works:
server$ rping -s -a 10.30.10.211 -v
server ping data: rdma-ping-0:
ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqr
server ping data: rdma-ping-1:
BCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrs
server DISCONNECT EVENT...
wait for RDMA_READ_ADV state 10
client$ rping -c -a 10.30.10.211 -C 2 -v
(output omitted)
But ibv_rc_pingpong doesn't
server$ ibv_rc_pingpong -d iwp____
local address: LID 0x0000, QPN 0x000001, PSN 0xb8aafc, GID ::
Failed to modify QP to RTS
Couldn't connect to remote QP
client$ ibv_rc_pingpong -d iwp____ 10.30.10.211
local address: LID 0x0000, QPN 0x000001, PSN 0x71abc5, GID ::
client read/write: Protocol not supported
Couldn't read/write remote address
dmesg says: [ 93.957733] iwpm_register_pid: Unable to send a nlmsg
(client = 2)
And OpenMPI/UCX doesn't want to use the transport either:
[1566564168.338103] [host:23059:0] select.c:410 UCX ERROR
no active messages transport to <no debug data>: mm/posix - Destination
is unreachable, mm/sysv - Destination is unreachable, self/self -
Destination is unreachable, rdmacm/sockaddr - no am bcopy, cma/cma - no
am bcopy
Is this a bug or a limitation of siw?
Thanks,
Marcin
On 22.08.2019 18:24, Marcin Mielniczuk wrote:
> Thanks a lot, this did the trick. I think this is worth documenting
> somewhere.
> Would README.md in the rdma-core repo be a good place?
>
> Why
>
> On 22.08.2019 17:52, Leon Romanovsky wrote:
>> On Thu, Aug 22, 2019 at 09:13:25PM +0530, Krishnamraju Eraparaju wrote:
>>> On Thursday, August 08/22/19, 2019 at 17:08:49 +0200, Marcin Mielniczuk wrote:
>>>> Hi,
>>>>
>>>> I'm trying to test the recently merged siw module.
>>>> I'm running kernel 5.3-rc5 (taken from the Ubuntu mainline-kernel
>>>> repository [1]) on Ubuntu 18.04 (bionic).
>>>> I also manually installed rdma-core 25.0 from tarball, using the
>>>> included Debian packaging. I installed all the packages but ibacm.
>>>>
>>>> After booting the new kernel I manually loaded the kernel module by
>>>>
>>>> modprobe siw
>>>> modprobe rdma_ucm
>>>>
>>>> Then ibv_devinfo shows: "No IB devices found".
>>>> dmesg only shows:
>>>> [ 29.856751] SoftiWARP attached
>>>>
>>>> According to this tutorial, [2] it should be enough to just load the siw
>>>> module. (unlike RXE, where one needs to use rxe_cfg to set up the
>>>> interface)
>>>> Is this a bug in siw or just a configuration issue on my side?
>>> Have you done "rdma link"?
>>>
>>> rdma link add <NAME> type siw netdev <NETDEV>
>>>
>>> http://man7.org/linux/man-pages/man8/rdma-link.8.html
>> BTW, the same goes for RXE and rxe_cfg is discouraged.
>>
>> Thanks
>>
>>>> Thanks,
>>>> Marcin
>>>>
>>>> [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc5/
>>>> [2] https://budevg.github.io/posts/tutorials/2017/04/29/rdma-101-1.html
>>>>
>
next prev parent reply other threads:[~2019-08-23 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 15:08 Setting up siw devices Marcin Mielniczuk
2019-08-22 15:43 ` Krishnamraju Eraparaju
2019-08-22 15:52 ` Leon Romanovsky
2019-08-22 17:05 ` Marcin Mielniczuk
2019-08-22 17:21 ` Leon Romanovsky
2019-08-22 17:58 ` Marcin Mielniczuk
2019-08-22 18:38 ` Leon Romanovsky
2019-08-22 19:13 ` Jason Gunthorpe
2019-08-22 19:24 ` Leon Romanovsky
2019-08-26 10:02 ` Marcin Mielniczuk
2019-08-26 11:39 ` Leon Romanovsky
2019-08-26 18:21 ` Marcin Mielniczuk
[not found] ` <b4bf4bc2-8dc7-a2c2-6bd2-ab41d9fbadc9@golem.network>
2019-08-23 14:17 ` Marcin Mielniczuk [this message]
2019-08-23 14:50 ` Jason Gunthorpe
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=945643c8-198e-f8bf-1e8f-536f77612db0@golem.network \
--to=marcin@golem.network \
--cc=krishna2@chelsio.com \
--cc=leon@kernel.org \
--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.