From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: pyverbs test regression
Date: Wed, 4 Nov 2020 11:06:55 -0600 [thread overview]
Message-ID: <ddac88a4-4a79-2685-d28d-301614a58644@gmail.com> (raw)
In-Reply-To: <OFB1D10315.3DD6DADF-ON00258616.004C490E-00258616.004C4915@notes.na.collabserv.com>
On 11/4/20 7:53 AM, Bernard Metzler wrote:
> -----"Bob Pearson" <rpearsonhpe@gmail.com> wrote: -----
>
>> To: "Jason Gunthorpe" <jgg@nvidia.com>, "Leon Romanovsky"
>> <leon@kernel.org>
>> From: "Bob Pearson" <rpearsonhpe@gmail.com>
>> Date: 11/04/2020 12:55AM
>> Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
>> Subject: [EXTERNAL] pyverbs test regression
>>
>> Since 5.10 some of the pyverbs tests are skipping with the warning
>> "Device rxe_0 doesn't have net interface"
>>
>> These occur in tests/test_rdmacm.py. As far as I can tell the error
>> occurs in
>>
>> RDMATestCase _add_gids_per_port after the following
>>
>> if not
>> os.path.exists('/sys/class/infiniband/{}/device/net/'.format(dev)):
>> self.args.append([dev, port, idx, None])
>> continue
>>
>> In fact there is no such path which means it never finds an ip_addr
>> for the device.
>>
>> Did something change here? Do other RDMA devices have
>> /sys/class/infiniband/XXX/device/net?
>>
>
> Hmm, with 5.10.0-rc1, I still see it for both rdma_rxe and siw.
>
Bernard,
The script I use to setup the rxe device is
export LD_LIBRARY_PATH=/home/rpearson/src/rdma-core/build/lib/
sudo ip link set dev enp6s0 mtu 4500
sudo ip addr add dev enp6s0 scope link fe80::b62e:99ff:fef9:fa2e/64
sudo rdma link add rxe_0 type rxe netdev enp6s0
After running this the rxe device is functional but I get
rpearson$ ls /sys/class/infiniband/rxe_0
fw_ver node_guid parent power sys_image_guid
node_desc node_type ports subsystem uevent
with no 'device'. How are you seeing 'device'? We should be running the same bits.
Bob
prev parent reply other threads:[~2020-11-04 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 23:54 pyverbs test regression Bob Pearson
2020-11-04 0:00 ` Jason Gunthorpe
2020-11-04 10:40 ` Edward Srouji
2020-11-04 11:47 ` Gal Pressman
2020-11-04 17:46 ` Bob Pearson
2020-11-04 12:36 ` Jason Gunthorpe
2020-11-04 18:34 ` Edward Srouji
2020-11-04 18:43 ` Jason Gunthorpe
2020-11-04 13:53 ` Bernard Metzler
2020-11-04 17:06 ` Bob Pearson [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=ddac88a4-4a79-2685-d28d-301614a58644@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=BMT@zurich.ibm.com \
--cc=jgg@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox