[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201018121640.jwzj6ivpis4gh4ki@skbuf>
Date: Sun, 18 Oct 2020 12:16:41 +0000
From: Vladimir Oltean <vladimir.oltean@....com>
To: Heiner Kallweit <hkallweit1@...il.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"andrew@...n.ch" <andrew@...n.ch>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"vivien.didelot@...il.com" <vivien.didelot@...il.com>,
"kuba@...nel.org" <kuba@...nel.org>,
Christian Eggers <ceggers@...i.de>,
Kurt Kanzenbach <kurt@...utronix.de>
Subject: Re: [RFC PATCH 01/13] net: dsa: add plumbing for custom netdev
statistics
On Sun, Oct 18, 2020 at 02:02:46PM +0200, Heiner Kallweit wrote:
> Wouldn't a simple unsigned long (like in struct net_device_stats) be
> sufficient here? This would make handling the counter much simpler.
> And as far as I understand we talk about a packet counter that is
> touched in certain scenarios only.
I don't understand, in what sense 'sufficient'? This counter is exported
to ethtool which works with u64 values, how would an unsigned long,
which is u32 on 32-bit systems, help?
Powered by blists - more mailing lists