From: patchwork-bot+netdevbpf@kernel•org
To: Mohsin Bashir <mohsin.bashr@gmail•com>
Cc: netdev@vger•kernel.org, alexanderduyck@fb•com,
alok.a.tiwari@oracle•com, andrew+netdev@lunn•ch, andrew@lunn•ch,
davem@davemloft•net, dg573847474@gmail•com,
donald.hunter@gmail•com, edumazet@google•com, gal@nvidia•com,
horms@kernel•org, idosch@nvidia•com, jacob.e.keller@intel•com,
kernel-team@meta•com, kory.maincent@bootlin•com, kuba@kernel•org,
lee@trager•us, leon@kernel•org, linux-kernel@vger•kernel.org,
linux-rdma@vger•kernel.org, linux@armlinux•org.uk,
mbloch@nvidia•com, mike.marciniszyn@gmail•com,
o.rempel@pengutronix•de, pabeni@redhat•com, saeedm@nvidia•com,
tariqt@nvidia•com, vadim.fedorenko@linux•dev
Subject: Re: [net-next V4 0/5] net: ethtool: Track TX pause storm
Date: Thu, 05 Mar 2026 15:40:16 +0000 [thread overview]
Message-ID: <177272521605.3175356.3608317280940155593.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260302230149.1580195-1-mohsin.bashr@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat•com>:
On Mon, 2 Mar 2026 15:01:44 -0800 you wrote:
> With TX pause enabled, if a device cannot deliver received frames to
> the stack (e.g., during a system hang), it may generate excessive pause
> frames causing a pause storm. This series updates the uAPI to track TX
> pause storm events as part of the pause stats (p1), proposes using the
> existing pfc-prevention-tout knob to configure the storm watchdog (p2),
> adds pause storm protection support for fbnic (p3), and leverages p1
> to provide observability into these events for the fbnic (p4) and mlx5
> (p5) drivers.
>
> [...]
Here is the summary with links:
- [net-next,V4,1/5] net: ethtool: Track pause storm events
https://git.kernel.org/netdev/net-next/c/cc39325f9278
- [net-next,V4,2/5] net: ethtool: Update doc for tunable
https://git.kernel.org/netdev/net-next/c/817de93c348a
- [net-next,V4,3/5] eth: fbnic: Add protection against pause storm
https://git.kernel.org/netdev/net-next/c/9b7c8728f53a
- [net-next,V4,4/5] eth: fbnic: Fetch TX pause storm stats
https://git.kernel.org/netdev/net-next/c/8d282b680c72
- [net-next,V4,5/5] eth: mlx5: Move pause storm errors to pause stats
https://git.kernel.org/netdev/net-next/c/cc663d3fed06
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-03-05 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 23:01 [net-next V4 0/5] net: ethtool: Track TX pause storm Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 1/5] net: ethtool: Track pause storm events Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 2/5] net: ethtool: Update doc for tunable Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 3/5] eth: fbnic: Add protection against pause storm Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 4/5] eth: fbnic: Fetch TX pause storm stats Mohsin Bashir
2026-03-02 23:01 ` [net-next V4 5/5] eth: mlx5: Move pause storm errors to pause stats Mohsin Bashir
2026-03-05 11:26 ` Paolo Abeni
2026-03-05 14:12 ` Tariq Toukan
2026-03-05 15:43 ` Mohsin Bashir
2026-03-05 15: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=177272521605.3175356.3608317280940155593.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexanderduyck@fb$(echo .)com \
--cc=alok.a.tiwari@oracle$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=dg573847474@gmail$(echo .)com \
--cc=donald.hunter@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=gal@nvidia$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=jacob.e.keller@intel$(echo .)com \
--cc=kernel-team@meta$(echo .)com \
--cc=kory.maincent@bootlin$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lee@trager$(echo .)us \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=mbloch@nvidia$(echo .)com \
--cc=mike.marciniszyn@gmail$(echo .)com \
--cc=mohsin.bashr@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=o.rempel@pengutronix$(echo .)de \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=tariqt@nvidia$(echo .)com \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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