From: Saeed Mahameed <saeed@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
Russell King <linux@armlinux.org.uk>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/5] net: add and use dev_get_tstats64
Date: Mon, 02 Nov 2020 14:36:43 -0800 [thread overview]
Message-ID: <4ca1f21d5f8a119fe6483df370b64af6a33e565e.camel@kernel.org> (raw)
In-Reply-To: <25c7e008-c3fb-9fcd-f518-5d36e181c0cb@gmail.com>
On Sun, 2020-11-01 at 13:33 +0100, Heiner Kallweit wrote:
> It's a frequent pattern to use netdev->stats for the less frequently
> accessed counters and per-cpu counters for the frequently accessed
> counters (rx/tx bytes/packets). Add a default ndo_get_stats64()
> implementation for this use case. Subsequently switch more drivers
> to use this pattern.
>
> Heiner Kallweit (5):
> net: core: add dev_get_tstats64 as a ndo_get_stats64 implementation
> net: make ip_tunnel_get_stats64 an alias for dev_get_tstats64
> ip6_tunnel: use ip_tunnel_get_stats64 as ndo_get_stats64 callback
> net: dsa: use net core stats64 handling
> tun: switch to net core provided statistics counters
>
not many left,
$ git grep dev_fetch_sw_netstats drivers/
drivers/infiniband/hw/hfi1/ipoib_main.c: dev_fetch_sw_netstats(s
torage, priv->netstats);
drivers/net/macsec.c: dev_fetch_sw_netstats(s, dev->tstats);
drivers/net/usb/qmi_wwan.c: dev_fetch_sw_netstats(stats, priv-
>stats64);
drivers/net/usb/usbnet.c: dev_fetch_sw_netstats(stats, dev-
>stats64);
drivers/net/wireless/quantenna/qtnfmac/core.c: dev_fetch_sw_netstats(s
tats, vif->stats64);
Why not convert them as well ?
macsec has a different implementation, but all others can be converted.
next prev parent reply other threads:[~2020-11-02 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 12:33 [PATCH net-next 0/5] net: add and use dev_get_tstats64 Heiner Kallweit
2020-11-01 12:34 ` [PATCH net-next 1/5] net: core: add dev_get_tstats64 as a ndo_get_stats64 implementation Heiner Kallweit
2020-11-02 21:09 ` Florian Fainelli
2020-11-01 12:35 ` [PATCH net-next 2/5] net: make ip_tunnel_get_stats64 an alias for dev_get_tstats64 Heiner Kallweit
2020-11-02 21:09 ` Florian Fainelli
2020-11-02 21:37 ` Jakub Kicinski
2020-11-02 21:56 ` Saeed Mahameed
2020-11-01 12:36 ` [PATCH net-next 3/5] ip6_tunnel: use ip_tunnel_get_stats64 as ndo_get_stats64 callback Heiner Kallweit
2020-11-01 12:37 ` [PATCH net-next 4/5] net: dsa: use net core stats64 handling Heiner Kallweit
2020-11-02 21:13 ` Florian Fainelli
2020-11-02 21:22 ` Vladimir Oltean
2020-11-01 12:38 ` [PATCH net-next 5/5] tun: switch to net core provided statistics counters Heiner Kallweit
2020-11-02 22:36 ` Saeed Mahameed [this message]
2020-11-03 14:46 ` [PATCH net-next 0/5] net: add and use dev_get_tstats64 Heiner Kallweit
2020-11-03 17:05 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ca1f21d5f8a119fe6483df370b64af6a33e565e.camel@kernel.org \
--to=saeed@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).