[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MWHPR11MB169342D6B1CC71B8805A741AEF179@MWHPR11MB1693.namprd11.prod.outlook.com>
Date: Fri, 2 Dec 2022 15:22:55 +0000
From: <Jerry.Ray@...rochip.com>
To: <kuba@...nel.org>
CC: <olteanv@...il.com>, <andrew@...n.ch>, <f.fainelli@...il.com>,
<davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<netdev@...r.kernel.org>
Subject: RE: [PATCH net-next v4] dsa: lan9303: Add 3 ethtool stats
>>
>> get_stats64 will require PHYLINK.
>
>Huh? I'm guessing you're referring to some patches you have queued
>already and don't want to rebase across? Or some project planning?
>Otherwise I don't see a connection :S
>
In looking around at other implementations, I see where the link_up
and link_down are used to start or clean up the periodic workqueue
used to retrieve and accumulate the mib stats into the driver. Can't tell
if that's a requirement or only needed when the device interface is
considered too slow. The device interface is not atomic.
J.
Powered by blists - more mailing lists