Re: [PATCH rtw-next v3 3/3] wifi: rtl8xxxu: preserve RX requests across recoverable transfer errors
From: Kim Wooseok
Date: Sun Sep 20 2026 - 04:18:22 EST
Hi Ping-Ke,
> 'retry' --> 'defer_schedule'?
Agreed, I will rename it to defer_schedule.
> Not prefer using bare system_wq.
> Can both use schedule_delayed_work()?
In v3, the error path uses queue_delayed_work(system_wq, ..., delay),
while normal completions use mod_delayed_work(system_wq, ..., 0).
I can replace the error-path call with schedule_delayed_work().
However, the normal-completion path is intended to bring an existing
delayed retry forward when the pending count exceeds the batching
threshold, which schedule_delayed_work(..., 0) cannot do because it
leaves an already pending timer unchanged.
Would it be OK to retain mod_delayed_work() for normal completions,
changing its queue argument to system_percpu_wq?
With that change, schedule_delayed_work() would select system_percpu_wq
internally, and mod_delayed_work() would use the same queue explicitly.
> nit: a blank line
I will add it before the switch.
Thanks,
Kim Wooseok