From: Breno Leitao <leitao@debian.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Amir Vadai <amirv@mellanox.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, dcostantino@meta.com,
rneu@meta.com, kernel-team@meta.com
Subject: Re: [PATCH net] net/mlx5e: Skip NAPI polling when PCI channel is offline
Date: Wed, 11 Feb 2026 07:17:28 -0800 [thread overview]
Message-ID: <aYycsIGsth4ob1sU@gmail.com> (raw)
In-Reply-To: <aYyHNGBPu0dEIEzS@gmail.com>
On Wed, Feb 11, 2026 at 05:44:56AM -0800, Breno Leitao wrote:
> On Wed, Feb 11, 2026 at 01:26:35PM +0200, Tariq Toukan wrote:
> > On 09/02/2026 20:01, Breno Leitao wrote:
> > If the problem is that the WARN_ON is being called at a high rate, then it
> > should be rate-limited.
>
> That would be a solution as well, and I am happy to pursue it, if that one is
> more appropriate
In fact, I got more inclined to try to fix it in iommu code, let's see how it
goes.
https://lore.kernel.org/all/20260211-dma_io_mmu-v1-1-cf89e24437af@debian.org/
--
pv-bot: closed
next prev parent reply other threads:[~2026-02-11 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 18:01 [PATCH net] net/mlx5e: Skip NAPI polling when PCI channel is offline Breno Leitao
2026-02-10 2:19 ` Jijie Shao
2026-02-10 15:18 ` Breno Leitao
2026-02-11 1:42 ` Jijie Shao
2026-02-11 11:26 ` Tariq Toukan
2026-02-11 13:44 ` Breno Leitao
2026-02-11 15:17 ` Breno Leitao [this message]
2026-02-11 15:27 ` Breno Leitao
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=aYycsIGsth4ob1sU@gmail.com \
--to=leitao@debian.org \
--cc=amirv@mellanox.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dcostantino@meta.com \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rneu@meta.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ttoukan.linux@gmail.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.