From: Breno Leitao <leitao@debian.org>
To: Zack Gomez <zack.gomez@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] netpoll: bound the deferred transmit queue
Date: Mon, 14 Sep 2026 01:47:39 -0700 [thread overview]
Message-ID: <aqeyvaw06I2883Fo@gmail.com> (raw)
In-Reply-To: <20260914041221.1028092-1-zack.gomez@gmail.com>
On Mon, Sep 14, 2026 at 12:12:21AM -0400, Zack Gomez wrote:
> A producer that outruns that drain therefore grows the queue until the
> host is out of memory.
...
> Observed with netconsole forwarding a GPU driver
> that logged one line at ~1e5/s after a firmware hang.
I know what you mean, I'm seeing the same issue on my side.
> Cap it at 1024 skbs and drop new skbs beyond that.
I don't think netpoll should be the one doing rate limiting here.
I think the rate limiting should live on the netconsole side, not
netpoll.
I have a patchset that does exactly that, which I wrote after
hitting a similar issue in production. Would you mind having a test?
https://lore.kernel.org/all/20260910-netcons_ratelimit-v2-0-ebf0dd91e26e@debian.org/
> @@ -314,6 +322,10 @@ static netdev_tx_t __netpoll_send_skb(struct netpoll *np, struct sk_buff *skb)
> }
>
> if (!dev_xmit_complete(status)) {
> + if (skb_queue_len(&npinfo->txq) >= NETPOLL_TXQ_MAX) {
> + dev_kfree_skb_irq(skb);
> + goto out;
If we do end up also rate limiting at the netpoll side, I'd like to
see a WARN_ON_ONCE() here, since it shouldn't be the main ratelimit
path, but rather something to flag that something is off.
--breno
next prev parent reply other threads:[~2026-09-14 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 4:12 [PATCH net] netpoll: bound the deferred transmit queue Zack Gomez
2026-09-14 8:47 ` Breno Leitao [this message]
2026-09-15 16:40 ` Zack Gomez
2026-09-15 16:45 ` Zack Gomez
2026-09-16 10:01 ` Breno Leitao
2026-09-22 14:41 ` Zack Gomez
2026-09-17 4:12 ` 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=aqeyvaw06I2883Fo@gmail.com \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zack.gomez@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.