From: patchwork-bot+netdevbpf@kernel.org
To: Erni Sri Satya Vennela <ernis@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
longli@microsoft.com, kotaranov@microsoft.com, horms@kernel.org,
shradhagupta@linux.microsoft.com, ssengar@linux.microsoft.com,
dipayanroy@linux.microsoft.com, shirazsaleem@microsoft.com,
sbhatta@marvell.com, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] net: mana: Refactor GF stats handling and add rx_missed_errors counter
Date: Tue, 18 Nov 2025 04:00:25 +0000 [thread overview]
Message-ID: <176343842550.3578356.18200043929984849136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1763120599-6331-1-git-send-email-ernis@linux.microsoft.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 14 Nov 2025 03:43:17 -0800 you wrote:
> Restructure mana_query_gf_stats() to operate on the per-VF mana_context,
> instead of per-port statistics. Introduce mana_ethtool_hc_stats to
> isolate hardware counter statistics and update the
> "ethtool -S <interface>" output to expose all relevant counters while
> preserving backward compatibility.
>
> Add support for the standard rx_missed_errors counter by mapping it to
> the hardware's hc_rx_discards_no_wqe metric. Introduce a
> global workqueue that refreshes statistics every 2 seconds, ensuring
> timely and consistent updates of hardware counters.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: mana: Move hardware counter stats from per-port to per-VF context
https://git.kernel.org/netdev/net-next/c/e275d9091c01
- [net-next,v3,2/2] net: mana: Add standard counter rx_missed_errors
https://git.kernel.org/netdev/net-next/c/be4f1d67ec56
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:[~2025-11-18 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 11:43 [PATCH net-next v3 0/2] net: mana: Refactor GF stats handling and add rx_missed_errors counter Erni Sri Satya Vennela
2025-11-14 11:43 ` [PATCH net-next v3 1/2] net: mana: Move hardware counter stats from per-port to per-VF context Erni Sri Satya Vennela
2025-11-16 21:50 ` Haiyang Zhang
2025-11-14 11:43 ` [PATCH net-next v3 2/2] net: mana: Add standard counter rx_missed_errors Erni Sri Satya Vennela
2025-11-16 21:50 ` Haiyang Zhang
2025-11-18 4:00 ` 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=176343842550.3578356.18200043929984849136.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=dipayanroy@linux.microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=shirazsaleem@microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.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 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.