From: Josef Bacik <josef@toxicpanda.com>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "Saeed Mahameed" <saeedm@nvidia.com>,
"Mark Bloch" <mbloch@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Jakub Kicinski" <kuba@kernel.org>,
"Björn Töpel" <bjorn@kernel.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net] net/mlx5e: Fix stalled channels with threaded NAPI
Date: Thu, 29 Oct 2026 15:15:00 +0000 [thread overview]
Message-ID: <17932869000000.4.mlx5e-threaded-napi-stall@toxicpanda.com> (raw)
In-Reply-To: <1a26c186-bba5-40f9-8cd9-3967b2b268bf@nvidia.com>
On Thu, Oct 29, 2026 at 02:52:06PM +0200, Tariq Toukan wrote:
> We confirmed it on the device, on ConnectX-6 Dx (the generation in your
> report) and on ConnectX-7: an arm raises an immediate event only when
> the CQ holds a CQE newer than the last reported event. A backlog the
> last event already reported raises nothing.
Thanks for checking that.
> Please hold your v2 until these are out, and rebase on top: your patch
> then stands as what it is, saving a complete-and-rearm cycle per budget
> with threaded NAPI.
Will do. Please Cc me on them. On top of your fix it is no longer a
fix, so v2 will drop the Fixes tag and go to net-next.
What changes in v2 besides that: the test moves into
mlx5e_channel_no_affinity_change(), as Jakub and Bjorn asked, and it
tests NAPI_STATE_SCHED_THREADED instead of NAPI_STATE_THREADED, so that
it follows who is polling and not the mode that was asked for.
> One request for the code comment when you reword it: today it reads as
> if arming never raises an event for pending CQEs, "only for a new
> completion".
The comment in v2 only says why the CPU of the NAPI thread tells
nothing about the interrupt's affinity, it no longer says anything
about arming. The changelog will use your wording.
pw-bot: cr
Thanks,
Josef
next prev parent reply other threads:[~2026-10-29 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 17:37 [PATCH net] net/mlx5e: Fix stalled channels with threaded NAPI Josef Bacik
2026-10-21 17:47 ` sashiko-bot
2026-10-21 19:10 ` Björn Töpel
2026-10-21 20:49 ` Jakub Kicinski
2026-10-22 11:38 ` Tariq Toukan
2026-10-22 12:56 ` Josef Bacik
2026-10-22 13:51 ` Tariq Toukan
2026-10-29 12:52 ` Tariq Toukan
2026-10-29 15:15 ` Josef Bacik [this message]
2026-10-25 18:49 ` netdev-bot+sashiko
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=17932869000000.4.mlx5e-threaded-napi-stall@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=andrew+netdev@lunn.ch \
--cc=bjorn@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 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.