From: Jakub Kicinski <kuba@kernel.org>
To: javen <javen_xu@realsil.com.cn>
Cc: <hkallweit1@gmail.com>, <nic_swsd@realtek.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v10 3/7] r8169: add support for new interrupt mapping
Date: Mon, 10 Aug 2026 14:29:28 -0700 [thread overview]
Message-ID: <20260810142928.0e53be5b@kernel.org> (raw)
In-Reply-To: <20260803021305.488-4-javen_xu@realsil.com.cn>
On Mon, 3 Aug 2026 10:13:01 +0800 javen wrote:
> +static int rtl8169_poll_msix_rx(struct napi_struct *napi, int budget)
> +{
> + struct net_device *dev = napi->dev;
> + struct rtl8169_private *tp;
> + int work_done = 0;
> + int message_id;
> +
> + tp = netdev_priv(dev);
> + message_id = napi - tp->rtl8169_napi;
> +
> + if (message_id < tp->num_rx_rings)
> + work_done += rtl_rx(dev, tp, &tp->rx_ring[message_id], budget, napi);
> +
> + if (work_done < budget && napi_complete_done(napi, work_done))
> + rtl8169_enable_hw_interrupt_msix(tp, message_id);
> +
> + return work_done;
> +}
> +
> +static int rtl8169_poll_msix_tx(struct napi_struct *napi, int budget)
> +{
> + struct net_device *dev = napi->dev;
> + struct rtl8169_private *tp;
> +
> + tp = netdev_priv(dev);
> +
> + rtl_tx(dev, tp, budget);
This seems not to be ring aware? Is that because we can only have 1 Tx
ring at this point? maybe add a comment to this effect, it's somewhat
unusual.
> + if (napi_complete_done(napi, 0))
> + rtl8169_enable_hw_interrupt_msix(tp, (int)(napi - tp->rtl8169_napi));
> +
> + return 0;
> +}
> +
> +static int rtl8169_poll_msix_other(struct napi_struct *napi, int budget)
> +{
> + struct net_device *dev = napi->dev;
> + struct rtl8169_private *tp;
> +
> + tp = netdev_priv(dev);
> +
> + if (napi_complete_done(napi, 0))
> + rtl8169_enable_hw_interrupt_msix(tp, (int)(napi - tp->rtl8169_napi));
Why are we using a NAPI for "other" ? NAPI is for packet processing.
This handler only acks the IRQ and does nothing (even after all the
later patches in the series, AFAICT) so why schedule the NAPI in the
first place, and not handle all the work in the IRQ directly?
> + return 0;
> +}
next prev parent reply other threads:[~2026-08-10 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 2:12 [PATCH net-next v10 0/7] r8169: add RSS support for RTL8127 javen
2026-08-03 2:12 ` [PATCH net-next v10 1/7] r8169: add support for multi irqs javen
2026-08-03 2:13 ` [PATCH net-next v10 2/7] r8169: refactor RX path to prepare for multi-queue javen
2026-08-10 21:26 ` Jakub Kicinski
2026-08-03 2:13 ` [PATCH net-next v10 3/7] r8169: add support for new interrupt mapping javen
2026-08-10 21:29 ` Jakub Kicinski [this message]
2026-08-03 2:13 ` [PATCH net-next v10 4/7] r8169: enable " javen
2026-08-10 21:31 ` Jakub Kicinski
2026-08-03 2:13 ` [PATCH net-next v10 5/7] r8169: add support and enable rss javen
2026-08-10 21:31 ` Jakub Kicinski
2026-08-10 21:38 ` Jakub Kicinski
2026-08-03 2:13 ` [PATCH net-next v10 6/7] r8169: move struct ethtool_ops javen
2026-08-03 2:13 ` [PATCH net-next v10 7/7] r8169: support setting rx queue numbers via ethtool javen
2026-08-10 21:41 ` Jakub Kicinski
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=20260810142928.0e53be5b@kernel.org \
--to=kuba@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=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;
as well as URLs for NNTP newsgroup(s).