From: Wei Fang <wei.fang@nxp.com>
To: claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: [PATCH net-next 0/3] change some statistics to 64-bit
Date: Fri, 20 Jun 2025 18:21:37 +0800 [thread overview]
Message-ID: <20250620102140.2020008-1-wei.fang@nxp.com> (raw)
The port MAC counters of ENETC are 64-bit registers and the statistics
of ethtool are also u64 type, so add enetc_port_rd64() helper function
to read 64-bit statistics from these registers, and also change the
statistics of ring to unsigned long type to be consistent with the
statistics type in struct net_device_stats.
Wei Fang (3):
net: enetc: change the statistics of ring to unsigned long type
net: enetc: separate 64-bit counters from enetc_port_counters
net: enetc: read 64-bit statistics from port MAC counters
drivers/net/ethernet/freescale/enetc/enetc.h | 22 ++---
.../ethernet/freescale/enetc/enetc_ethtool.c | 99 +++++++++++--------
.../net/ethernet/freescale/enetc/enetc_hw.h | 1 +
3 files changed, 68 insertions(+), 54 deletions(-)
--
2.34.1
next reply other threads:[~2025-06-20 10:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:21 Wei Fang [this message]
2025-06-20 10:21 ` [PATCH net-next 1/3] net: enetc: change the statistics of ring to unsigned long type Wei Fang
2025-06-20 12:51 ` Claudiu Manoil
2025-06-21 9:52 ` Simon Horman
2025-06-23 1:49 ` Wei Fang
2025-06-23 16:28 ` Simon Horman
2025-06-24 1:34 ` Wei Fang
2025-06-20 10:21 ` [PATCH net-next 2/3] net: enetc: separate 64-bit counters from enetc_port_counters Wei Fang
2025-06-20 12:51 ` Claudiu Manoil
2025-06-21 10:36 ` Simon Horman
2025-06-23 3:13 ` Wei Fang
2025-06-23 16:32 ` Simon Horman
2025-06-20 10:21 ` [PATCH net-next 3/3] net: enetc: read 64-bit statistics from port MAC counters Wei Fang
2025-06-20 12:51 ` Claudiu Manoil
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=20250620102140.2020008-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoning.wang@nxp.com \
/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