Messages in this thread |  | | | Date | Fri, 20 Jul 2012 01:01:34 +0900 (JST) | | From | Round Robinjp <> | | Subject | workqueue and kworker |
| |
Hi 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? Thanks RR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |