From: netdev-bot+sashiko@kernel.org
To: javen_xu@realsil.com.cn
Cc: hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, 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-next v15 4/7] r8169: enable new interrupt mapping
Date: Thu, 01 Oct 2026 16:06:46 +0000 [thread overview]
Message-ID: <179087080624.434549.12502317761885183568@kernel.org> (raw)
In-Reply-To: <20260928070423.202-5-javen_xu@realsil.com.cn>
Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.
Low priority / nit picks for your consideration:
- [Low] The commit message says the patch "enables new interrupt mapping
for RTL8127", but at this commit the new code can never run.
--
r8169: enable new interrupt mapping
This patch adds a helper that sets INT_CFG0_ENABLE_8125 to turn on the
new interrupt vector mapping for RTL8127. It also moves the rx error,
dropped, length, crc and multicast counters from dev->stats into per rx
ring u64_stats counters, and sums them in rtl8169_get_stats64().
> r8169: enable new interrupt mapping
>
> This patch enables new interrupt mapping for RTL8127 and add error pkts
> counter per ring.
> diff --git a/drivers/net/ethernet/realtek/r8169_main.c b/drivers/net/ethernet/realtek/r8169_main.c
> index 4656ae108f9c6..20eb7987f03dc 100644
> --- a/drivers/net/ethernet/realtek/r8169_main.c
> +++ b/drivers/net/ethernet/realtek/r8169_main.c
[ ... ]
> @@ -4092,6 +4111,9 @@ static void rtl_hw_start_8125_common(struct rtl8169_private *tp)
> RTL_W32(tp, RSS_CTRL_8125, 0);
> RTL_W16(tp, Q_NUM_CTRL_8125, 0);
>
> + if (tp->irq_nvecs > 1)
> + rtl8169_hw_enable_vec_mapping(tp);
> +
[Severity: Low]
Can this branch be taken at this point in the series?
At this commit, rtl_alloc_irq() still asks for exactly one vector:
rtl_alloc_irq() {
...
nvecs = pci_alloc_irq_vectors(pdev, 1, 1, flags);
...
}
so tp->irq_nvecs is always 1, and rtl8169_hw_enable_vec_mapping() never
runs.
rtl_setup_rx_params() also still sets:
tp->num_rx_rings = 1;
so the new per-ring counter loop in rtl8169_get_stats64() only ever
covers ring 0.
The next patch in the series ("r8169: add support and enable rss") adds
get_min_irq_nvecs()/get_max_irq_nvecs() and rtl8169_set_rx_ring_num().
Only after that does the mapping actually get enabled for RTL8127.
This isn't a bug, but could the commit message say that the mapping
enable stays dormant until a later patch allocates more than one vector,
rather than saying this patch enables it?
> /* disable UPS */
> r8168_mac_ocp_modify(tp, 0xd40a, 0x0010, 0x0000);
[ ... ]
--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260928070423.202-1-javen_xu%40realsil.com.cn
next prev parent reply other threads:[~2026-10-01 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 7:04 [PATCH net-next v15 0/7] r8169: add RSS support for RTL8127 javen
2026-09-28 7:04 ` [PATCH net-next v15 1/7] r8169: prepare for multi irqs and napi javen
2026-10-01 16:06 ` netdev-bot+sashiko
2026-09-28 7:04 ` [PATCH net-next v15 2/7] r8169: refactor RX path to prepare for multi-queue javen
2026-10-01 16:06 ` netdev-bot+sashiko
2026-09-28 7:04 ` [PATCH net-next v15 3/7] r8169: add support for new interrupt mapping javen
2026-10-01 16:06 ` netdev-bot+sashiko
2026-09-28 7:04 ` [PATCH net-next v15 4/7] r8169: enable " javen
2026-10-01 16:06 ` netdev-bot+sashiko [this message]
2026-09-28 7:04 ` [PATCH net-next v15 5/7] r8169: add support and enable rss javen
2026-10-01 16:06 ` netdev-bot+sashiko
2026-09-28 7:04 ` [PATCH net-next v15 6/7] r8169: move struct ethtool_ops javen
2026-09-28 7:04 ` [PATCH net-next v15 7/7] r8169: add get_channel support for ethtool javen
2026-10-01 16:06 ` 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=179087080624.434549.12502317761885183568@kernel.org \
--to=netdev-bot+sashiko@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®