All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pearson, Robert B" <robert.pearson2@hpe.com>
To: Alexander Kalentyev <comrad.karlovich@gmail.com>,
	Yanjun Zhu <yanjun.zhu@linux.dev>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: RE: rdma_rxe usage problem
Date: Wed, 19 Jan 2022 19:54:14 +0000	[thread overview]
Message-ID: <PH7PR84MB14880DAC2578D1CBFAC7CC87BC599@PH7PR84MB1488.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CABrV9YuiYkCKMBMsrnd38ZxwqxJeWMw+xXFRpXc1gMtdAN9bFA@mail.gmail.com>



-----Original Message-----
From: Alexander Kalentyev <comrad.karlovich@gmail.com> 
Sent: Wednesday, January 19, 2022 11:53 AM


Anyway the ibv_rc_pingpong shows an error:

>ibv_rc_pingpong -d rxe0 -g 0
  local address:  LID 0x0000, QPN 0x000015, PSN 0x015dd8, GID
fe80::4a51:c5ff:fef6:e159
Failed to modify QP to RTR
Couldn't connect to remote QP

>
Alexander,

I use a script to restart rxe after changing anything it looks like

	#!/bin/bash

	export LD_LIBRARY_PATH=<path to rdma-core>/rdma-core/build/lib:/usr/lib

	sudo rmmod rdma_rxe
	sudo modprobe rdma_rxe

	sudo ip link set dev enp0s3 mtu 4500
	sudo ip addr add dev enp0s3 fe80::0a00:27ff:fe35:5ea7/64
	sudo rdma link add rxe0 type rxe netdev enp0s3

The important line is adding the ipv6 address which corresponds with the MAC address of
The ethernet nic which is

	08:00:27:35:5e:a7

Some OSes (like mine) do not create this address automatically but mangle the address.
But the rdma core driver seems to expect all roce providers to have it.

Hope this helps.

Bob Pearson
rpearson@hpe.com

  reply	other threads:[~2022-01-19 19:55 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
2022-01-19 17:53   ` Alexander Kalentyev
2022-01-19 19:54     ` Pearson, Robert B [this message]
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=PH7PR84MB14880DAC2578D1CBFAC7CC87BC599@PH7PR84MB1488.NAMPRD84.PROD.OUTLOOK.COM \
    --to=robert.pearson2@hpe.com \
    --cc=comrad.karlovich@gmail.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjun.zhu@linux.dev \
    /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.