Re: [PATCH] sched: Further restrict the preemption modes

[Ciunas Bennett]

> > delayed significantly before it gets CPU time.
>
> There is some work done by Marco to rework the API to explicitly state
> if a per-CPU workqueue is mandatory _or_ if an CPU unbound workqueue can
> be used instead. (Rather than having schedule_work() not knowing the
> implications).

Oh, that is good some work already being done here.
I had a small patch ready to go, but possibly the solution needs to be more robust.
-            schedule_work(&irqfd->inject);
+            queue_work(system_dfl_wq, &irqfd->inject);


> It seems that using an unbound worker would avoid the problem at hand,
> correct?
>
> Sebastian

Yeah, changing to an unbound kworker avoids the issue in any of the testing I have done.
Ciunas