Taylor R Campbell <[email protected]> wrote: > We don't have a nice easy lightweight way for a driver to ask that a > task be executed asynchronously in thread context. The closest we > have is workqueue(9), but each user has to do bookkeeping for a > different workqueue and incurs a long-term kthread, or ncpu long-term > kthreads, that are mostly idle -- most users of workqueue(9) create a > single struct work for the workqueue and use it for a single purpose. > > <...>
Not against the idea, but frankly - the implementation looks somewhat over-engineered. Why not to extend the workqueue(9) interface in the first place? -- Mindaugas
