[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR11MB1693E002721F0696949C5DCBEF159@MWHPR11MB1693.namprd11.prod.outlook.com>
Date: Wed, 30 Nov 2022 15:51:44 +0000
From: <Jerry.Ray@...rochip.com>
To: <kuba@...nel.org>
CC: <andrew@...n.ch>, <f.fainelli@...il.com>, <olteanv@...il.com>,
<davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH net-next v3] dsa: lan9303: Add 3 ethtool stats
>On Mon, 28 Nov 2022 14:55:21 -0600 Jerry Ray wrote:
>> These statistics are maintained by the switch and count the packets
>> dropped due to buffer limits. Note that the rtnl_link_stats: rx_dropped
>> statistic does not include dropped packets due to buffer exhaustion and as
>> such, part of this counter would more appropriately fall under the
>> rx_missed_errors.
>
>Why not add them there as well?
>
>Are these drops accounted for in any drop / error statistics within
>rtnl_link_stats?
>
>It's okay to provide implementation specific breakdown via ethtool -S
>but user must be able to notice that there are some drops / errors in
>the system by looking at standard stats.
>
The idea here is to provide the statistics as documented in the part
datasheet. In the future, I'll be looking to add support for the stats64
API and will deal with appropriately sorting the available hardware stats
into the rtnl_link_stats buckets.
Regards,
Jerry.
Powered by blists - more mailing lists