From: Justin Lai <justinlai0215@realtek.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
Ping-Ke Shih <pkshih@realtek.com>,
Larry Chiu <larry.chiu@realtek.com>
Subject: RE: [PATCH] rtase: Reset TX subqueue when clearing TX ring
Date: Tue, 2 Jun 2026 10:06:50 +0000 [thread overview]
Message-ID: <611cbfc8d2ac46a0bb0d1f3b42091bd0@realtek.com> (raw)
In-Reply-To: <7a5702ba-af01-485d-84fb-f54c9d5269b2@intel.com>
> From: Justin Lai <justinlai0215@realtek.com>
> Date: Mon, 1 Jun 2026 14:24:18 +0800
>
> > rtase_tx_clear() clears the TX ring and resets the ring indexes.
> > However, the TX queue state and BQL accounting are not reset at the
> > same time.
> >
> > This may leave __QUEUE_STATE_STACK_XOFF asserted after
> > rtase_sw_reset(), preventing new TX packets from being scheduled.
> >
> > Reset the TX subqueue when clearing the TX ring so the TX queue state
> > and BQL accounting are restored together.
> >
> > Signed-off-by: Justin Lai <justinlai0215@realtek.com>
>
> You need to:
>
> 1. Specify the target branch in the subject prefix ([PATCH net]
> for critical fixes, [PATCH net-next] for features and misc
> non-critical fixes and improvements).
> 2. If this is a fix targeting "net", you need to provide a "Fixes:"
> tag pointing to the commit which introduced this issue.
> 3. If this is a fix and the bug is present in older supported kernels
> (LTSes etc), you need to add "Cc: stable@vger.kernel.org" right
> after the "Fixes:" tag.
>
> > ---
> > drivers/net/ethernet/realtek/rtase/rtase_main.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > index 43a4aa275b62..11e9d0feea68 100644
> > --- a/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > +++ b/drivers/net/ethernet/realtek/rtase/rtase_main.c
> > @@ -240,6 +240,8 @@ static void rtase_tx_clear(struct rtase_private *tp)
> > rtase_tx_clear_range(ring, ring->dirty_idx,
> RTASE_NUM_DESC);
> > ring->cur_idx = 0;
> > ring->dirty_idx = 0;
> > +
> > + netdev_tx_reset_subqueue(tp->dev, i);
>
> The fix itself looks ok.
>
> > }
> > }
>
> Thanks,
> Olek
Hi Olek,
Thanks for the review.
This is a bug fix. I'll resend it targeting the net tree with
the proper Fixes tag and Cc stable@vger.kernel.org.
Thanks,
Justin
prev parent reply other threads:[~2026-06-02 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 6:24 [PATCH] rtase: Reset TX subqueue when clearing TX ring Justin Lai
2026-06-01 13:19 ` Alexander Lobakin
2026-06-02 10:06 ` Justin Lai [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=611cbfc8d2ac46a0bb0d1f3b42091bd0@realtek.com \
--to=justinlai0215@realtek.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkshih@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