net: usb: r8152: fix transmit queue timeout
Subsystems (4)
PATCH 1/1 net: usb: r8152: fix transmit queue timeout
When the TX queue length reaches the threshold, the netdev watchdog immediately detects a TX queue timeout.
This patch updates the transmit queue's trans_start timestamp upon completion of each asynchronous USB URB submission on the TX path, ensuring the network watchdog correctly reflects ongoing transmission activity.
--- drivers/net/usb/r8152.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/usb/r8152.c +2 -0
@@ -1954,6 +1954,8 @@ static void write_bulk_callback(struct urb *urb)if (!skb_queue_empty (&tp->tx_queue))tasklet_schedule (&tp->tx_tl); + +netif_trans_update (netdev); }static void intr_callback (struct urb *urb)
Signature · 1 line
2.34.1
insyelu <[email protected]>
Quoted 1 line
Sent: Wednesday, January 14, 2026 10:56 AM
[...]
Quoted 18 lines
When the TX queue length reaches the threshold, the netdev watchdog immediately detects a TX queue timeout.
This patch updates the transmit queue's
trans_starttimestamp upon completion of each asynchronous USB URB submission on the TX path, ensuring the network watchdog correctly reflects ongoing transmission activity.Signed-off-by insyelu <[email protected]>--- drivers/net/usb/r8152.c | 2 ++ 1 file changed, 2 insertions(+)drivers/net/usb/r8152.c +0
-0
drivers/net/usb/r8152.c static void write_bulk_callback(struct urb *urb) · line 1959
Quoted 6 lines
drivers/net/usb/r8152.c +2
-0@@ -1954,6 +1954,8 @@ static void write_bulk_callback(struct urb *urb)if (!skb_queue_empty (&tp->tx_queue))tasklet_schedule (&tp->tx_tl); + +netif_trans_update (netdev); }
Based on the definition of netif_trans_update(), I think it would be better to move it into tx_agg_fill(). Such as
drivers/net/usb/r8152.c +2 -0
@@ -2449,6 +2449,8 @@ static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg) ret =usb_submit_urb (agg->urb,GFP_ATOMIC );if (ret <0 )usb_autopm_put_interface_async (tp->intf); +else +netif_trans_update (tp->netdev); out_tx_fill:return ret;
Best Regards,
Hayes
Quoted 23 lines · Hayes Wang <[email protected]> 于2026年1月14日周三 12:38写道:
insyelu <[email protected]>
Quoted 1 line
Sent: Wednesday, January 14, 2026 10:56 AM
[...]
Quoted 19 lines
When the TX queue length reaches the threshold, the netdev watchdog immediately detects a TX queue timeout.
This patch updates the transmit queue's
trans_starttimestamp upon completion of each asynchronous USB URB submission on the TX path, ensuring the network watchdog correctly reflects ongoing transmission activity.Signed-off-by insyelu <[email protected]>--- drivers/net/usb/r8152.c | 2 ++ 1 file changed, 2 insertions(+)drivers/net/usb/r8152.c +0
-0@@ -1954,6 +1954,8 @@ static void write_bulk_callback(struct urb *urb)
Quoted 8 lines
drivers/net/usb/r8152.c static void write_bulk_callback(struct urb *urb) · line 1959
Quoted 5 lines
drivers/net/usb/r8152.c +2
-0if (!skb_queue_empty (&tp->tx_queue))tasklet_schedule (&tp->tx_tl); + +netif_trans_update (netdev); }Based on the definition of
netif_trans_update(), I think it would be better to move it intotx_agg_fill(). Such as
HI Hayes Wang,
To reduce the performance impact on the tx_tl tasklet’s transmit path, netif_trans_update() has been moved from the main transmit path into write_bulk_callback (the USB transfer completion callback). The main considerations are as follows:
1. Reduce frequent tasklet overheadnetif_trans_update() is invoked frequently under high-throughput conditions. Calling it directly in the main transmit path continuously introduces a small but noticeable CPU overhead, degrading the scheduling efficiency of the tx_tl tasklet.
2. Move non-critical operations out of the critical path
By deferring netif_trans_update() to the USB callback thread—and ensuring it executes after tasklet_schedule(&tp->tx_tl)—the timestamp update is removed from the critical transmit scheduling path, further reducing the burden on tx_tl.
3. This design follows the approach used in mature USB NIC drivers such as rtl8150
Although it is semantically more intuitive to call netif_trans_update() at the point where tx_agg_fill is defined, delaying the timestamp update is both reasonable and safe from a performance standpoint—the network watchdog mechanism only requires a coarse indication that “a transmission occurred recently” and does not require strict synchronization with the submission time of each individual packet.
If strict semantic consistency is preferred, I am happy to resubmit a patch that aligns with the above rationale.
Best Regards,
insyelu
Quoted 16 lines
drivers/net/usb/r8152.c +2
-0@@ -2449,6 +2449,8 @@ static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg) ret =usb_submit_urb (agg->urb,GFP_ATOMIC );if (ret <0 )usb_autopm_put_interface_async (tp->intf); +else +netif_trans_update (tp->netdev); out_tx_fill:return ret;Best Regards,
Hayes
lu lu <[email protected]>
Quoted 1 line
Sent: Thursday, January 15, 2026 9:37 AM
[...]
Quoted 6 lines
To reduce the performance impact on the
tx_tltasklet’s transmit path,netif_trans_update()has been moved from the main transmit path intowrite_bulk_callback(the USB transfer completion callback). The main considerations are as follows:
1. Reduce frequent tasklet overheadnetif_trans_update()is invoked frequently under high-throughput
Quoted 8 lines
conditions. Calling it directly in the main transmit path continuously introduces a small but noticeable CPU overhead, degrading the scheduling efficiency of the
tx_tltasklet.
2. Move non-critical operations out of the critical path
By deferringnetif_trans_update()to the USB callback thread—and ensuring it executes after tasklet_schedule(&tp->tx_tl)—the timestamp update is removed from the critical transmit scheduling path, further reducing the burden ontx_tl.
Excuse me, I do not fully understand the reasoning above.
It seems that this change merely shifts the time (or effort) from tx_tl to the TX completion callback.
While the intention is to make tx_tl run faster, this also delays the completion of the callback, which in turn may delay both the next callback execution and the next scheduling of tx_tl.
From this perspective, it is unclear what is actually being saved.
Have you observed a measurable difference based on testing?
If you want to reduce the frequency of calling netif_trans_update(), you could try something like the following. This way, netif_trans_update() would not be executed on every transmission.
drivers/net/usb/r8152.c +5 -2
@@ -2432,9 +2432,12 @@ static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg)netif_tx_lock (tp->netdev); -if (netif_queue_stopped (tp->netdev) && -skb_queue_len (&tp->tx_queue) < tp->tx_qlen) +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); + }netif_tx_unlock (tp->netdev);
Best Regards,
Hayes
Quoted 22 lines · Hayes Wang <[email protected]> 于2026年1月15日周四 19:42写道:
lu lu <[email protected]>
Quoted 1 line
Sent: Thursday, January 15, 2026 9:37 AM
[...]
Quoted 6 lines
To reduce the performance impact on the
tx_tltasklet’s transmit path,netif_trans_update()has been moved from the main transmit path intowrite_bulk_callback(the USB transfer completion callback). The main considerations are as follows:
1. Reduce frequent tasklet overheadnetif_trans_update()is invoked frequently under high-throughputQuoted 8 lines
conditions. Calling it directly in the main transmit path continuously introduces a small but noticeable CPU overhead, degrading the scheduling efficiency of the
tx_tltasklet.
2. Move non-critical operations out of the critical path
By deferringnetif_trans_update()to the USB callback thread—and ensuring it executes after tasklet_schedule(&tp->tx_tl)—the timestamp update is removed from the critical transmit scheduling path, further reducing the burden ontx_tl.Excuse me, I do not fully understand the reasoning above.
It seems that this change merely shifts the time (or effort) fromtx_tlto the TX completion callback.
Quoted 6 lines
While the intention is to make
tx_tlrun faster, this also delays the completion of the callback, which in turn may delay both the next callback execution and the next scheduling oftx_tl.From this perspective, it is unclear what is actually being saved.
Have you observed a measurable difference based on testing?
HW: RK3399-based development board (dual-core Cortex-A72 + quad-core Cortex-A53)
OS: LEDE (OpenWrt)
NIC: 2.5G USB Ethernet adapter connected via USB 3.0
Due to platform performance limitations, it cannot reach 2.5G. When processing in the write_bulk_callback and during USB submission, iperf3 stress testing shows a difference of approximately 8Mbit/s. This may be related to the platform's big.LITTLE core configuration.
Quoted 9 lines
If you want to reduce the frequency of calling
netif_trans_update(), you could try something like the following. This way,netif_trans_update()would not be executed on every transmission.drivers/net/usb/r8152.c +0
-0@@ -2432,9 +2432,12 @@ static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg)
drivers/net/usb/r8152.c static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg) · line 2440
Quoted 10 lines
drivers/net/usb/r8152.c +5
-2netif_tx_lock (tp->netdev); -if (netif_queue_stopped (tp->netdev) && -skb_queue_len (&tp->tx_queue) < tp->tx_qlen) +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); + }
The queue was stopped because it exceeded the threshold. Attempting to refresh the time at this point is clearly too late.
Thank you for your suggestion. I will submit v2 (immediately updating the transfer start time after successful USB submission).
Best Regards,
insyelu
Quoted 6 lines
drivers/net/usb/r8152.c +0
-0netif_tx_unlock (tp->netdev); Best Regards,Hayes
lu lu <[email protected]>
Quoted 1 line
Sent: Friday, January 16, 2026 10:11 AM
[...]
Quoted 10 lines
drivers/net/usb/r8152.c static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg) · line 2440
Quoted 10 lines
netif_tx_lock(tp->netdev);drivers/net/usb/r8152.c +5
-2-if (netif_queue_stopped (tp->netdev) && -skb_queue_len (&tp->tx_queue) < tp->tx_qlen) +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); + }
Quoted 2 lines
The queue was stopped because it exceeded the threshold. Attempting to refresh the time at this point is clearly too late.
Why would this be considered too late?
Based on RTL8152_TX_TIMEOUT, there are about 5 seconds to wake the queue or update the timestamp before a TX timeout occurs. I believe 5 seconds should be sufficient.
If there is no TX submission for 5 seconds after the driver stops the queue, then something is already wrong.
Best Regards,
Hayes
Quoted 14 lines · Hayes Wang <[email protected]> 于2026年1月16日周五 11:11写道:
lu lu <[email protected]>
Quoted 1 line
Sent: Friday, January 16, 2026 10:11 AM
[...]
Quoted 10 lines
Quoted 10 lines
netif_tx_lock(tp->netdev);drivers/net/usb/r8152.c +5
-2-if (netif_queue_stopped (tp->netdev) && -skb_queue_len (&tp->tx_queue) < tp->tx_qlen) +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); + }
Quoted 4 lines
Quoted 2 lines
The queue was stopped because it exceeded the threshold. Attempting to refresh the time at this point is clearly too late.
Why would this be considered too late?
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);
}The first time xmit stops the transmit queue, the queue is not full, and it is successfully woken up afterward — OK.
The second time xmit stops the transmit queue, the network watchdog times out immediately because the transmit timestamp was not refreshed when the queue was last resumed — FAIL.
This scenario is logically possible.
There is no clear evidence that netif_trans_update imposes a significant CPU load.
Please help me review:
https://patchwork.kernel.org/project/linux-usb/patch/[email protected]
Quoted 11 lines
Based on
RTL8152_TX_TIMEOUT, there are about 5 seconds to wake the queue or update the timestamp before a TX timeout occurs. I believe 5 seconds should be sufficient.If there is no TX submission for 5 seconds after the driver stops the queue, then something is already wrong.
Best Regards,
Hayes
Original Message-----
Quoted 1 line
From: lu lu <[email protected]>
[...]
Quoted 6 lines
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);
}Quoted 6 lines
The first time xmit stops the transmit queue, the queue is not full, and it is successfully woken up afterward — OK.
The second time xmit stops the transmit queue, the network watchdog times out immediately because the transmit timestamp was not refreshed when the queue was last resumed — FAIL.
This scenario is logically possible.
This situation should not happen, because trans_start is also updated when the driver stops the TX queue.
https://elixir.bootlin.com/linux/v6.18.6/source/include/linux/netdevice.h#L3629
A TX timeout occurs only if the TX queue has been stopped for longer than RTL8152_TX_TIMEOUT. It should not occur immediately when the driver stops the TX queue.
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.
Best Regards,
Hayes
Quoted 17 lines · Hayes Wang <[email protected]> 于2026年1月19日周一 10:51写道:
Original Message-----
Quoted 1 line
From: lu lu <[email protected]>
[...]
Quoted 6 lines
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); }Quoted 6 lines
The first time xmit stops the transmit queue, the queue is not full, and it is successfully woken up afterward — OK.
The second time xmit stops the transmit queue, the network watchdog times out immediately because the transmit timestamp was not refreshed when the queue was last resumed — FAIL.
This scenario is logically possible.
Quoted 6 lines
This situation should not happen, because
trans_startis also updated when the driver stops the TX queue.https://elixir.bootlin.com/linux/v6.18.6/source/include/linux/netdevice.h#L3629
A TX timeout occurs only if the TX queue has been stopped for longer than
RTL8152_TX_TIMEOUT. It should not occur immediately when the driver stops the TX queue.
Thank you for the correction! Upon review, I confirmed that netif_tx_stop_queue() already updates trans_start,
so the timeout scenario I originally envisioned does not actually occur.
Quoted 3 lines
Therefore, what needs to be done is to update the timestamp when the TX queue is stopped. Updating
trans_startwhile 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.
Best regards,
insyelu
lu lu <[email protected]>
Quoted 1 line
Sent: Monday, January 19, 2026 2:58 PM
[...]
Quoted 8 lines
Quoted 2 lines
Therefore, what needs to be done is to update the timestamp when the TX queue is stopped. Updating
trans_startwhile 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); }
Quoted 7 lines
This change continuously updates the
trans_startvalue, 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
PATCH v2 1/1 net: usb: r8152: fix transmit queue timeout
In reply to insyeluWhen the TX queue length reaches the threshold, the netdev watchdog immediately detects a TX queue timeout.
This patch updates the trans_start timestamp of the transmit queue on every asynchronous USB URB submission along the transmit path, ensuring that the network watchdog accurately reflects ongoing transmission activity.
---
v2: Update the transmit timestamp when submitting the USB URB.
--- drivers/net/usb/r8152.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/usb/r8152.c +2 -0
@@ -2449,6 +2449,8 @@ static int r8152_tx_agg_fill(struct r8152 *tp, struct tx_agg *agg) ret =usb_submit_urb (agg->urb,GFP_ATOMIC );if (ret <0 )usb_autopm_put_interface_async (tp->intf); +else +netif_trans_update (tp->netdev); out_tx_fill:return ret;
Signature · 1 line
2.34.1
Quoted 11 lines · insyelu
When the TX queue length reaches the threshold, the netdev watchdog immediately detects a TX queue timeout.
This patch updates the
trans_starttimestamp of the transmit queue on every asynchronous USB URB submission along the transmit path, ensuring that the network watchdog accurately reflects ongoing transmission activity.Signed-off-by insyelu <[email protected]>---
v2: Update the transmit timestamp when submitting the USB URB.
Always create a new thread for a new version of a patch. The CI/CD system just thinks this is a discussion comment, so has ignored it.
Andrew
---
pw-bot: cr