linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Tom Talpey <tom@talpey.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	Bernard Metzler <bmt@zurich.ibm.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH] Add missing ib_uverbs dependency from SoftiWARP
Date: Wed, 7 Sep 2022 11:06:09 -0300	[thread overview]
Message-ID: <YxilUf2HbA6PAo59@nvidia.com> (raw)
In-Reply-To: <0b035368-5da3-73c6-4d6f-1e22bcc70ecb@talpey.com>

On Wed, Sep 07, 2022 at 09:57:43AM -0400, Tom Talpey wrote:

> You can test it easily, just load siw on a laptop without any
> other RDMA provider. The ib_uverbs module will not be loaded,
> and the siw provider won't be seen, rping -s will run but peers
> cannot connect for example.

Perhaps there is something funky with rping, it works fine in simpler cases:

$ rdma link show
link siw0/1 state ACTIVE physical_state LINK_UP netdev enp0s31f6 
$ sudo rmmod ib_uverbs
$ build/bin/ibv_devinfo
hca_id:	siw0
	transport:			iWARP (1)
	fw_ver:				0.0.0
	node_guid:			7686:e2ff:fe28:63fc
	sys_image_guid:			7486:e228:63fc:0000
	vendor_id:			0x626d74
	vendor_part_id:			1
	hw_ver:				0x0
	phys_port_cnt:			1
		port:	1
			state:			PORT_ACTIVE (4)
			max_mtu:		1024 (3)
			active_mtu:		1024 (3)
			sm_lid:			0
			port_lid:		0
			port_lmc:		0x00
			link_layer:		Ethernet
$ lsmod | grep -i uverb
ib_uverbs             163840  0
ib_core               393216  2 ib_uverbs,siw

Jason


  reply	other threads:[~2022-09-07 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 13:45 [PATCH] Add missing ib_uverbs dependency from SoftiWARP Tom Talpey
2022-09-07 13:51 ` Jason Gunthorpe
2022-09-07 13:57   ` Bernard Metzler
2022-09-07 13:57   ` Tom Talpey
2022-09-07 14:06     ` Jason Gunthorpe [this message]
2022-09-07 15:24       ` Tom Talpey
2022-09-07 16:48         ` Jason Gunthorpe
2022-09-07 17:54           ` Tom Talpey

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=YxilUf2HbA6PAo59@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=bmt@zurich.ibm.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=tom@talpey.com \
    /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;
as well as URLs for NNTP newsgroup(s).