Hello, On Tue, Mar 29, 2022 at 10:33:19AM +0200, Rasmus Villemoes wrote: > On 29/03/2022 08.30, Sebastian Andrzej Siewior wrote: > > On 2022-03-28 07:39:25 [-1000], Tejun Heo wrote: > >> Hello, > > Hi, > > > >> I wonder whether it'd be useful to provide a set of wrappers which can make > >> switching between workqueue and kworker easy. Semantics-wise, they're > >> already mostly aligned and it shouldn't be too difficult to e.g. make an > >> unbounded workqueue be backed by a dedicated kthread_worker instead of > >> shared pool depending on a flag, or even allow switching dynamically. > > Well, that would certainly not make it any easier for userspace to > discover the thread it needs to chrt(). Each workqueue have a name and it's not difficult to make dedicated workers created this way to inherit the name. From user's pov, it's not that complicated - if kttyd (or whatever) is present, the user can twiddle with its scheduling class and priority. Thanks. -- tejun
