From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: alexanderduyck@fb.com, kuba@kernel.org, kernel-team@meta.com,
andrew+netdev@lunn.ch, davem@davemloft.net, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, sdf@fomichev.me, edumazet@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] eth: mpnic: add basic netdev statistics
Date: Wed, 21 Oct 2026 08:40:06 +0000 [thread overview]
Message-ID: <179257200678.486685.1500275130118777466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261012-mpnic-counters3-v2-0-8afba81c2d5a@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 12 Oct 2026 05:04:33 -0700 you wrote:
> Add basic netdev statistics and report them via ndo_get_stats64 and
> netdev_stat_ops.
>
> Track per queue netdev statistics such as Tx/Rx: packets, bytes, drops,
> etc. The driver keeps per-queue state for statistics that is updated
> mostly from the NAPI poll and ndo_start_xmit paths. The stats are made
> available through the usual driver APIs.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] eth: mpnic: count packets, bytes, and drops per ring
https://git.kernel.org/netdev/net-next/c/554c7af9367a
- [net-next,v2,2/4] eth: mpnic: report per-queue stats
https://git.kernel.org/netdev/net-next/c/5cc79ff41b07
- [net-next,v2,3/4] eth: mpnic: count Tx queue stops and wakes
https://git.kernel.org/netdev/net-next/c/3b28e126619f
- [net-next,v2,4/4] eth: mpnic: count Rx allocation failures
https://git.kernel.org/netdev/net-next/c/ce0d47658920
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-21 8:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 12:04 [PATCH net-next v2 0/4] eth: mpnic: add basic netdev statistics Daniel Zahka
2026-10-12 12:04 ` [PATCH net-next v2 1/4] eth: mpnic: count packets, bytes, and drops per ring Daniel Zahka
2026-10-13 12:05 ` netdev-bot+sashiko
2026-10-13 12:10 ` Daniel Zahka
2026-10-16 22:09 ` Sebastian Andrzej Siewior
2026-10-19 13:04 ` Daniel Zahka
2026-10-19 21:54 ` Sebastian Andrzej Siewior
2026-10-20 2:05 ` Jakub Kicinski
2026-10-20 21:21 ` Sebastian Andrzej Siewior
2026-10-20 21:34 ` Daniel Zahka
2026-10-20 21:50 ` Jakub Kicinski
2026-10-21 8:26 ` Paolo Abeni
2026-10-12 12:04 ` [PATCH net-next v2 2/4] eth: mpnic: report per-queue stats Daniel Zahka
2026-10-13 12:05 ` netdev-bot+sashiko
2026-10-13 13:30 ` Daniel Zahka
2026-10-20 2:00 ` Jakub Kicinski
2026-10-12 12:04 ` [PATCH net-next v2 3/4] eth: mpnic: count Tx queue stops and wakes Daniel Zahka
2026-10-12 12:04 ` [PATCH net-next v2 4/4] eth: mpnic: count Rx allocation failures Daniel Zahka
2026-10-21 8:40 ` patchwork-bot+netdevbpf [this message]
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=179257200678.486685.1500275130118777466.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel.zahka@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.