From: Jakub Kicinski <kuba@kernel.org>
To: Parav Pandit <parav@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
Shay Drori <shayd@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH net-next] devlink: Improve the port attributes description
Date: Fri, 27 Dec 2024 10:19:24 -0800 [thread overview]
Message-ID: <20241227101924.48a12733@kernel.org> (raw)
In-Reply-To: <PH8PR12MB72088C3633116EA320A55B5FDC032@PH8PR12MB7208.namprd12.prod.outlook.com>
On Tue, 24 Dec 2024 03:40:34 +0000 Parav Pandit wrote:
> > On Thu, 19 Dec 2024 17:01:58 +0200 Parav Pandit wrote:
> > > Improve the description of devlink port attributes PF, VF and SF
> > > numbers.
> >
> > Please provide more context. It's not obvious why you remove PF from
> > descriptions but not VF or SF.
>
> 'PF number' was vague and source of confusion. Some started thinking that it is some kind of index like how VF number is an index.
> So 'PF number' is rewritten to bring the clarity that it's the function number of the PCI device which is very will described in the PCI spec.
Just to make sure I understand - you're trying to emphasize that
the PF number is just an arbitrary ID of the PCIe PF within the chip,
not necessarily related to any BDF numbering sequence?
If that's the case I think the motivation makes sense. But IMHO
the execution is not ideal, I offer the fact we're having this
exchange as a proof of the point not getting across :(
May be better to explain this in a couple of sentences somewhere
(actually I get the feeling we already have such an explanation
but I can't find it. Perhaps it was just talked about on the list)
and then just point to that longer explanation in the attr kdocs?
> For VF number, the description is added describing it's an index starting from 0 (unlike pci spec where vf number starts from 1).
> SF number is user supplied number so nothing to remove there.
nit: -EOUTLOOK.. please wrap the lines in your replies at 80 chars.
next prev parent reply other threads:[~2024-12-27 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:01 [PATCH net-next] devlink: Improve the port attributes description Parav Pandit
2024-12-20 17:13 ` Samudrala, Sridhar
2024-12-23 18:09 ` Jakub Kicinski
2024-12-24 3:40 ` Parav Pandit
2024-12-27 18:19 ` Jakub Kicinski [this message]
2024-12-28 3:33 ` Parav Pandit
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=20241227101924.48a12733@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shayd@nvidia.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).