From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: Leon Romanovsky <leonro@nvidia.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: Mon, 9 Nov 2020 13:57:00 -0400 [thread overview]
Message-ID: <20201109175700.GF244516@ziepe.ca> (raw)
In-Reply-To: <7a9866b6-fa33-0b95-4bda-4c83112be369@amazon.com>
On Mon, Nov 09, 2020 at 11:03:47AM +0200, Gal Pressman wrote:
> > The thing is, is is still useless. You have to consult sysfs to
> > understand what bus it is scoped on to do anything further with
> > it. Can't just assume it is PCI.
>
> This can be solved with Parav's suggestion.
Now you are adding more stuff.
What is wrong with reading sysfs? sysfs is where topology information
lives, why do we need to denormalize things?
Jason
next prev parent reply other threads:[~2020-11-09 17: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
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 [this message]
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=20201109175700.GF244516@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=leonro@nvidia.com \
--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