Hello, Sebastian. On Tue, Jan 30, 2024 at 11:20:11AM +0100, Sebastian Andrzej Siewior wrote: > If one context creates multiple work item which are then moved to > tasklet I don't see the difference vs workqueue with a bh_disable() > around it. The main difference is that it avoids scheduling latencies in scenarios where softirq isn't heavily loaded. > Looking at the USB changes, I would prefer to see it converted to > threaded interrupts instead of using tasklet or workqueue. Both > approaches (current tasklet, suggested workqueue) lose the original > context where the request was created. Having threaded interrupts would > allow to keep everything in the same "context" so you could prioritize > according to your needs. That's great. If threaded IRQs or even regular workqueues are suitable, that should be fine. This conversion is just targeted at the use cases which can benefit from executing in the softirq context. Thanks. -- tejun
