Some of them can probably. Or rather many depending on the configuration.
Sometimes there are good reasons for an own thread, but often there are also
bad reasons.
If the threads don't sleep or have special requirements long they
should generally just use keventd instead.
Unfortunately a lot of people seem to think they're cheap because
it's relatively easy to create them using work queues now, so we end
up with more and more all the time.
Especially on systems with many cores or threads which end up with a
lot of dubious per CPU threads. Some scaling up is needed, but one per CPU
seems to be generally too many.
My favourite for a ridiculous thread was and is "kpsmoused"
-Andi
-
