From: Geert Uytterhoeven <geert@linux-m68k.org>
To: iugfdin@proton.me
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
hkallweit1@gmail.com, kuba@kernel.org, netdev@vger.kernel.org,
nic_swsd@realtek.com, pabeni@redhat.com
Subject: Re: [PATCH net 0/2] r8169: fix checksum eligibility and failed TX batch progress
Date: Sun, 11 Oct 2026 14:30:26 +0200 [thread overview]
Message-ID: <20261011123026.12896-1-geert@linux-m68k.org> (raw)
In-Reply-To: <179098478409.1174319.4377246796187959500.r8169-cover@proton.me>
Hi iugfdin,
Thanks for your series!
> This series fixes two TX-path issues found while investigating a report
> of loss with an RTL8125D 2.5GbE controller (PCI revision 0c, XID 688).
Do you have a link to that report?
> The first patch preserves hardware checksum eligibility when a packet is
> already at least as long as the padding target. The second ensures that
> a failed skb does not leave previously committed xmit_more packets
> without a transmit poll request.
>
> Neither patch is claimed to resolve the reported physical packet loss.
> The reporter observed 10-20% loss, particularly at 2.5 Gb/s, while a
> vendor Realtek driver/firmware combination worked. No affected NIC was
> available in the development environment. The reporter identified the
> loaded firmware as rtl8125d-1_0.0.7 10/15/24. A possible firmware-related
> cause of the reported loss remains under separate investigation.
I haven't tested your series, but without it, I see 40% packet loss at
2.5Gbps on the same controller revision, when rtl8125d-1.fw from
linux-firmware is loaded[1]. Forcing a lower speed of 1 Gbps work fine.
With that firmware file moved out of the way, i.e. using the built-in
firmware, 2.5 Gbps works fine for me, too...
[1] "RTL8125D breaks at 2.5Gbps"
https://lore.kernel.org/CAMuHMdXPAeHoeaQbM9rXbXukoMbFV+0k28n6sRMw8XF8720WUA@mail.gmail.com/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2026-10-11 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 0:07 [PATCH net 0/2] r8169: fix checksum eligibility and failed TX batch progress iugfdin
2026-10-03 0:07 ` [PATCH net 1/2] r8169: preserve checksum offload when packet padding is unnecessary iugfdin
2026-10-07 15:34 ` Simon Horman
2026-10-08 0:27 ` Jakub Kicinski
2026-10-03 0:08 ` [PATCH net 2/2] r8169: flush pending transmit packets when an skb is dropped iugfdin
2026-10-07 15:34 ` Simon Horman
2026-10-11 12:30 ` Geert Uytterhoeven [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=20261011123026.12896-1-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=iugfdin@proton.me \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox