[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd80f6df5c184549a3705efa61d40d58@realtek.com>
Date: Mon, 19 Jan 2026 12:34:15 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: lu lu <insyelu@...il.com>
CC: "andrew+netdev@...n.ch" <andrew+netdev@...n.ch>,
"davem@...emloft.net"
<davem@...emloft.net>,
nic_swsd <nic_swsd@...ltek.com>, "tiwai@...e.de"
<tiwai@...e.de>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] net: usb: r8152: fix transmit queue timeout
lu lu <insyelu@...il.com>
> Sent: Monday, January 19, 2026 2:58 PM
[...]
> > Therefore, what needs to be done is to update the timestamp when the TX queue is stopped.
> > Updating trans_start while the TX queue is not stopped is useless.
> if (netif_queue_stopped(tp->netdev)) {
> if (skb_queue_len(&tp->tx_queue) < tp->tx_qlen)
> netif_wake_queue(tp->netdev);
> else
> netif_trans_update(tp->netdev);
> }
> This change continuously updates the trans_start value, even when the
> TX queue has been stopped and its length exceeds the threshold.
> This may prevent the watchdog timer from ever timing out, thereby
> masking potential transmission stall issues.
>
> The timestamp should be updated only upon successful URB submission to
> accurately reflect that the transport layer is still operational.
Although I think a URB error and a transmission stall are different,
I am fine with the simpler approach in v2.
Best Regards,
Hayes
Powered by blists - more mailing lists