[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR12MB6075B6ACD47B7707087522AAA5FD9@SJ1PR12MB6075.namprd12.prod.outlook.com>
Date: Thu, 12 Jan 2023 18:50:16 +0000
From: Aurelien Aptel <aaptel@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"sagi@...mberg.me" <sagi@...mberg.me>, "hch@....de" <hch@....de>,
"kbusch@...nel.org" <kbusch@...nel.org>,
"axboe@...com" <axboe@...com>,
Chaitanya Kulkarni <chaitanyak@...dia.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"aurelien.aptel@...il.com" <aurelien.aptel@...il.com>,
Shai Malin <smalin@...dia.com>,
"malin1024@...il.com" <malin1024@...il.com>,
Or Gerlitz <ogerlitz@...dia.com>,
Yoray Zack <yorayz@...dia.com>,
Boris Pismenny <borisp@...dia.com>
Subject: RE: [PATCH v8 03/25] net/ethtool: add ULP_DDP_{GET,SET} operations
for caps and stats
Hi Jakub,
> -----Original Message-----
> The implementation of stats is not what I had in mind.
> None of the stats you listed under "Statistics" in the documentation look nVidia
> specific. The implementation should look something like the pause frame stats
> (struct ethtool_pause_stats etc) but you can add the dynamic string set if you
> like.
>
> If given implementation does not support one of the stats it will not fill in the
> value and netlink will skip over it. The truly vendor- -specific stats (if any) can go
> to the old ethtool -S.
Do you mean that we could use the dynamic string approach and just define the counters names in netlink?
Our concern is that it will not allow us to have those stats per queue (as we do in the mlx patches), in
that case we can suggest reusing ethtool -Q option to request per-queue stats.
What do you think?
Thanks,
Powered by blists - more mailing lists