It's getting a bit repetitive but I really wanna steer people away from implementing separate kthreads for wrong reasons. kthread is surprisingly difficult to get right especially around freezing / exiting / hotplugs and people get it subtly wrong very often. On Thu, Jan 03, 2013 at 03:52:21PM -0500, J. Bruce Fields wrote: > No, I meant I was happy having my workqueue handled by a single > dedicated thread, which I don't see a trivial way to do any more. Because you don't need that. The old workqueue didn't give you anything better than the current one. It was usually more difficult to get right in terms of execution dependency because it introduced a lot of unintended execution dependencies through one-(per-cpu)-worker-per-workqueue rule. If anyone can show me workqueue is deadlocking when it shouldn't I'll be happy to look into it and fix it, but, up until now, most if not all reported cases were through incorrect usage, and things definitely don't work like described in this thread. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
