workqueue and kworker

From: Round Robinjp
Date: Thu Jul 19 2012 - 12:08:18 EST

It seems that even if you create a dedicated workqueue
in your driver, it does not give you a dedicated
kworker thread. Is this normal behaviour?
If so, then what is the difference between using
generic workqueue and dedicated workqueue?
I need to set the priority of my kworker thread high
(a specific value). For that I called sched_setscheduler()
in my workqueue handler. But I found that other
workqueues are also being executed on my high priority
kworker thread which is unexpected.
How do I give high priority to my kworker thread
without affecting the behaviour of other workqueues?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at