All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Marcin Mielniczuk <marcin@golem.network>
Cc: Krishnamraju Eraparaju <krishna2@chelsio.com>,
	linux-rdma@vger.kernel.org
Subject: Re: Setting up siw devices
Date: Thu, 22 Aug 2019 21:38:07 +0300	[thread overview]
Message-ID: <20190822183807.GN29433@mtr-leonro.mtl.com> (raw)
In-Reply-To: <b46f158f-61c9-b949-9174-ec110dc92f9a@golem.network>

On Thu, Aug 22, 2019 at 07:58:56PM +0200, Marcin Mielniczuk wrote:
> On 22.08.2019 19:21, Leon Romanovsky wrote:
> > On Thu, Aug 22, 2019 at 07:05:12PM +0200, Marcin Mielniczuk wrote:
> >> Thanks a lot, this did the trick. I think this is worth documenting
> >> somewhere that this step is needed.
> >> I'll make a PR, would README.md in the rdma-core repo be a good place?
> > I'm not so sure, but it is better to have in some place instead of not having at all.
> I think it's the first place one would look for some information. I'll
> make a PR today or tomorrow.
> >> Does <NAME> have any significance? I did:
> >>
> >>      sudo rdma link add siw0 type siw netdev enpXsYYfZ
> >>
> >> but the resulting device is called iwpXsYYfZ. I couldn't find a trace of
> >> `siw0` anywhere.
> > I would say that it is a bug in kernel part of SIW, because kernel rename
> > (the thing which change your siw0 to be iw* name) is looking for absence
> > of mentioning PCI inside of /sys/class/infiniband/siw0/*
> > https://github.com/linux-rdma/rdma-core/blob/master/kernel-boot/rdma_rename.c#L378
> I don't have /sys/class/infiniband/siw0 on my system, only
> /sys/class/infiniband/iwpXsYYfZ.
> iwp probably comes from iWARP.

Your iwpXsYYfZ was siw0 before rdma_rename was executed.

I can't test the patch now, but hope that this change below will fix your problem.

diff --git a/drivers/infiniband/sw/siw/siw_main.c b/drivers/infiniband/sw/siw/siw_main.c
index 05a92f997f60..38c25a26dfb2 100644
--- a/drivers/infiniband/sw/siw/siw_main.c
+++ b/drivers/infiniband/sw/siw/siw_main.c
@@ -326,21 +326,6 @@ static struct siw_device *siw_device_create(struct net_device *netdev)
 	struct device *parent = netdev->dev.parent;
 	int rv;

-	if (!parent) {
-		/*
-		 * The loopback device has no parent device,
-		 * so it appears as a top-level device. To support
-		 * loopback device connectivity, take this device
-		 * as the parent device. Skip all other devices
-		 * w/o parent device.
-		 */
-		if (netdev->type != ARPHRD_LOOPBACK) {
-			pr_warn("siw: device %s error: no parent device\n",
-				netdev->name);
-			return NULL;
-		}
-		parent = &netdev->dev;
-	}
 	sdev = ib_alloc_device(siw_device, base_dev);
 	if (!sdev)
 		return NULL;


  reply	other threads:[~2019-08-22 18:38 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 [this message]
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
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=20190822183807.GN29433@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=krishna2@chelsio.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=marcin@golem.network \
    /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.