Re: [RFC v4 1/2] workqueue: Add support for real-time workers

From: Tejun Heo

Date: Tue Sep 08 2026 - 18:55:32 EST


Hello,

On Mon, Sep 07, 2026 at 04:00:47PM +0100, Tvrtko Ursulin wrote:
> I thought it was more elegant to split the policy from the priority
> within a policy for call sites which only look up the policy.

I'd prefer a single priority value. NORMAL and HIGH use the same policy, and
nice already determines their priority. With both fields in the pool
attributes, otherwise identical unbound queues with the same nice level
cannot share a pool if one is NORMAL and the other HIGH. rt_prio() can keep
the RT checks simple.

> I did not quite manage to follow you here. Was this not the per cpu
> part, with unbound and ordered down lower?

Yes, I was confused. Please disregard that comment.

> I suppose this landed by now? I can see some changes so once we clarify
> the above opens I will rebase and adjust.

The shared allocation path is in wq/for-7.4 now. Please rebase on that.
Per-cpu pools are still separate, but RT can remain unbound-only without
waiting for the rest of the unification. Converting the shared priority
field still needs the corresponding updates to per-cpu/BH initialization and
priority checks.

Thanks.

--
tejun