From: Leon Romanovsky <leonro@nvidia.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Gal Pressman <galpress@amazon.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/nldev: Add parent bdf to device information dump
Date: Tue, 3 Nov 2020 15:57:19 +0200 [thread overview]
Message-ID: <20201103135719.GK5429@unreal> (raw)
In-Reply-To: <20201103134522.GL36674@ziepe.ca>
On Tue, Nov 03, 2020 at 09:45:22AM -0400, Jason Gunthorpe wrote:
> On Tue, Nov 03, 2020 at 03:26:27PM +0200, Gal Pressman wrote:
> > Add the ability to query the device's bdf through rdma tool netlink
> > command (in addition to the sysfs infra).
> >
> > In case of virtual devices (rxe/siw), the netdev bdf will be shown.
>
> Why? What is the use case?
Right, and why isn't netdev (RDMA_NLDEV_ATTR_NDEV_NAME) enough?
Thanks
>
> Jason
next prev parent reply other threads:[~2020-11-03 13:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 13:26 [PATCH for-next] RDMA/nldev: Add parent bdf to device information dump Gal Pressman
2020-11-03 13:31 ` Parav Pandit
2020-11-03 13:45 ` Jason Gunthorpe
2020-11-03 13:57 ` Leon Romanovsky [this message]
2020-11-03 14:11 ` Gal Pressman
2020-11-03 14:22 ` Jason Gunthorpe
2020-11-03 15:45 ` Gal Pressman
2020-11-05 20:00 ` Jason Gunthorpe
2020-11-08 13:03 ` Gal Pressman
2020-11-08 14:36 ` Parav Pandit
2020-11-08 23:49 ` Jason Gunthorpe
2020-11-09 5:09 ` Leon Romanovsky
2020-11-09 9:03 ` Gal Pressman
2020-11-09 11:55 ` Leon Romanovsky
2020-11-09 12:27 ` Gal Pressman
2020-11-09 12:32 ` Leon Romanovsky
2020-11-09 12:47 ` Gal Pressman
2020-11-09 13:02 ` Leon Romanovsky
2020-11-09 13:52 ` Gal Pressman
2020-11-09 14:12 ` Leon Romanovsky
2020-11-09 9:03 ` Gal Pressman
2020-11-09 17:57 ` Jason Gunthorpe
2020-11-10 7:49 ` Gal Pressman
2020-11-10 13:41 ` Jason Gunthorpe
2020-11-10 13:54 ` Leon Romanovsky
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=20201103135719.GK5429@unreal \
--to=leonro@nvidia.com \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=jgg@ziepe.ca \
--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.