From: Stephen Hemminger <stephen@networkplumber.org>
To: Howard Wang <howard_wang@realsil.com.cn>
Cc: <dev@dpdk.org>, <pro_nic_dpdk@realtek.com>
Subject: Re: [PATCH v1 0/6] net/r8169: hardware updates, optimizations, and a bug fix
Date: Thu, 11 Jun 2026 09:46:57 -0700 [thread overview]
Message-ID: <20260611094657.4299136a@phoenix.local> (raw)
In-Reply-To: <20260611083521.20669-1-howard_wang@realsil.com.cn>
On Thu, 11 Jun 2026 16:28:27 +0800
Howard Wang <howard_wang@realsil.com.cn> wrote:
> This patch series primarily focuses on updating hardware configurations,
> optimizing the datapath, and refining device behaviors for the net/r8169 PMD.
> Additionally, it includes one bug fix for a segmentation fault encountered
> during initialization.
>
> Summary of the series:
>
> - Patch 1: Updates RX CRC drop behavior for RTL8125BP and later MAC versions
> to align with device shutdown sequences and prevent cross-driver states.
> - Patch 2: Optimizes the Tx datapath performance by removing redundant branch
> checks for malformed packets, replacing them with RTE_ASSERT.
> - Patch 3: Enhances RTL8125+ flow control by utilizing a new formula for
> nearfull and nearempty thresholds.
> - Patch 4: Removes RTL9151 CSI (DBI) channel support, as firmware handling
> latency makes it no longer suitable for the driver.
> - Patch 5: Updates PHY and MAC MCU configurations for RTL9151A and RTL8125BP.
> - Patch 6: Fixes a segmentation fault during RTL8168 initialization by
> restricting RTL8125-specific RSS/VMQ configurations to the correct hardware.
>
> Howard Wang (6):
> net/r8169: disable RX CRC drop for RTL8125BP and later
> net/r8169: optimize Tx datapath by removing redundant packet checks
> net/r8169: improve RTL8125+ flow control
> net/r8169: remove RTL9151 CSI (DBI) channel support
> net/r8169: update hardware configurations for 8125
> net/r8169: fix segmentation fault during RTL8168 initialization
>
> drivers/net/r8169/base/rtl8125bp_mcu.c | 15 ++--
> drivers/net/r8169/base/rtl9151a.c | 8 +++
> drivers/net/r8169/base/rtl9151a_mcu.c | 14 +++-
> drivers/net/r8169/r8169_compat.h | 1 +
> drivers/net/r8169/r8169_hw.c | 98 ++++++++++++++++++++++++--
> drivers/net/r8169/r8169_hw.h | 2 +-
> drivers/net/r8169/r8169_rxtx.c | 32 ++++-----
> 7 files changed, 137 insertions(+), 33 deletions(-)
>
Looks good, the CI AI review complaints are noise and will ignore those.
Applied to next-net
prev parent reply other threads:[~2026-06-11 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 8:28 [PATCH v1 0/6] net/r8169: hardware updates, optimizations, and a bug fix Howard Wang
2026-06-11 8:28 ` [PATCH v1 1/6] net/r8169: disable RX CRC drop for RTL8125BP and later Howard Wang
2026-06-11 8:28 ` [PATCH v1 2/6] net/r8169: optimize Tx datapath by removing redundant packet checks Howard Wang
2026-06-11 8:28 ` [PATCH v1 3/6] net/r8169: improve RTL8125+ flow control Howard Wang
2026-06-11 8:28 ` [PATCH v1 4/6] net/r8169: remove RTL9151 CSI (DBI) channel support Howard Wang
2026-06-11 8:28 ` [PATCH v1 5/6] net/r8169: update hardware configurations for 8125 Howard Wang
2026-06-11 8:28 ` [PATCH v1 6/6] net/r8169: fix segmentation fault during RTL8168 initialization Howard Wang
2026-06-11 16:46 ` Stephen Hemminger [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=20260611094657.4299136a@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=howard_wang@realsil.com.cn \
--cc=pro_nic_dpdk@realtek.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