From: Sean Anderson <sean.anderson@linux.dev>
To: Andrew Lunn <andrew@lunn.ch>,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
netdev@vger.kernel.org
Cc: Simon Horman <horms@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
Michal Simek <michal.simek@amd.com>,
linux-kernel@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH net-next v3 0/2] net: xilinx: axienet: Add statistics support
Date: Thu, 15 Aug 2024 10:40:29 -0400 [thread overview]
Message-ID: <20240815144031.4079048-1-sean.anderson@linux.dev> (raw)
Add support for hardware statistics counters (if they are enabled) in
the AXI Ethernet driver. Unfortunately, the implementation is
complicated a bit since the hardware might only support 32-bit counters.
Changes in v3:
- Use explicit mutex_lock/unlock instead of guard() in
__axienet_device_reset to make it clear that we need to hold
lp->stats_lock for the whole function.
Changes in v2:
- Switch to a seqlock-based implementation to allow fresher updates
(rather than always using stale counter values from the previous
refresh).
- Take stats_lock unconditionally in __axienet_device_reset
- Fix documentation mismatch
Sean Anderson (2):
net: xilinx: axienet: Report RxRject as rx_dropped
net: xilinx: axienet: Add statistics support
drivers/net/ethernet/xilinx/xilinx_axienet.h | 85 ++++++
.../net/ethernet/xilinx/xilinx_axienet_main.c | 267 +++++++++++++++++-
2 files changed, 348 insertions(+), 4 deletions(-)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2024-08-15 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 14:40 Sean Anderson [this message]
2024-08-15 14:40 ` [PATCH net-next v3 1/2] net: xilinx: axienet: Report RxRject as rx_dropped Sean Anderson
2024-08-15 14:40 ` [PATCH net-next v3 2/2] net: xilinx: axienet: Add statistics support Sean Anderson
2024-08-17 2:42 ` Jakub Kicinski
2024-08-20 14:23 ` Sean Anderson
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=20240815144031.4079048-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.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;
as well as URLs for NNTP newsgroup(s).