[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<PH8PR12MB72088C3633116EA320A55B5FDC032@PH8PR12MB7208.namprd12.prod.outlook.com>
Date: Tue, 24 Dec 2024 03:40:34 +0000
From: Parav Pandit <parav@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "jiri@...nulli.us"
<jiri@...nulli.us>, "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>, "pabeni@...hat.com"
<pabeni@...hat.com>, "horms@...nel.org" <horms@...nel.org>, Shay Drori
<shayd@...dia.com>, Mark Bloch <mbloch@...dia.com>, Jiri Pirko
<jiri@...dia.com>
Subject: RE: [PATCH net-next] devlink: Improve the port attributes description
Hi Jakub,
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Monday, December 23, 2024 11:40 PM
>
> 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.
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.
Powered by blists - more mailing lists