Hello, On Mon, Jul 06, 2026 at 01:20:49PM +0100, Tvrtko Ursulin wrote: ... > > So the first question I would like to see considered is whether > > workqueue could be improved in any way to address said latency issues. > > > > Have you already considered that, Tvrtko? > > Yes, priority inheritance was justifiably rejected for generic workqueues. > There is WQ_HIGHPRI, but the idea here is to go one step further and allow > tracking realtime scheduling policies.
If deciding at work item boundaries is granular enough, it's not unconscionable to support RT worker pools. The main reason for resisting that is because it can be too easy to abuse. A couple RT threads may solve immediate problems but with a bunch of them you just don't have a working scheduler in the system. In general, it's pretty suspicious if there's intersection of "I need a bunch of worker threads in a flexible way" and "I want RT". How big a hit is WQ_HIGHPRI vs. RT? Thanks. -- tejun
