Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Keno Fischer <keno@juliahub.com>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, petrm@nvidia.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] mlxsw: spectrum_ethtool: expose per-PG rx_discards
Date: Thu, 21 May 2026 00:20:06 +0000	[thread overview]
Message-ID: <177932280665.3806355.5077784295396573616.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <agqkMwgM1PdkyMUR@juliahub.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 18 May 2026 01:31:31 -0400 you wrote:
> PPCNT group 0x10 (per-priority counters) carries an rx_discards field at
> offset 0x78. These counters aggregate up into if_in_discards, but don't
> show up anywhere else. Since there are many things that aggregate into
> `if_in_discards`, having these counters helps distinguish what caused
> those discards (in my case they were caused by headroom buffer overruns
> due to inappropriately configured buffer sizes).
> 
> [...]

Here is the summary with links:
  - [net-next] mlxsw: spectrum_ethtool: expose per-PG rx_discards
    https://git.kernel.org/netdev/net-next/c/a2b5e31b668f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-05-21  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  5:31 [PATCH net-next] mlxsw: spectrum_ethtool: expose per-PG rx_discards Keno Fischer
2026-05-18 17:19 ` Petr Machata
2026-05-19 22:50   ` Keno Fischer
2026-05-21  0:20 ` 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=177932280665.3806355.5077784295396573616.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=keno@juliahub.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@nvidia.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