From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH] net: r8169: drain RX descriptor ring
Date: Wed, 04 Mar 2026 08:48:54 +0100 [thread overview]
Message-ID: <177261053495.3897308.6153512092977413139.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260302172630.2713540-1-s.hauer@pengutronix.de>
On Mon, 02 Mar 2026 18:26:30 +0100, Sascha Hauer wrote:
> When not busy waiting for incoming packets we poll for new packets only
> every 10ms. Each time only a single frame is fetched from the hardware.
> On a network with many broadcast traffic there might be more than
> 100 packets/s incoming, which will sooner or later fill up our RX descriptor
> ring. Unfortunately the Realtek Hardware has no way to gracefully handle
> a RX queue overflow. Fix this by fetching multiple packets from the
> hardware in each receive callback.
>
> [...]
Applied, thanks!
[1/1] net: r8169: drain RX descriptor ring
https://git.pengutronix.de/cgit/barebox/commit/?id=ba8dab21987b (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-03-04 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 17:26 Sascha Hauer
2026-03-04 7:48 ` Sascha Hauer [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=177261053495.3897308.6153512092977413139.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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