On Wed, Jul 22, 2015 at 07:24:46AM +0200, Mike Galbraith wrote: > WORK_CPU_UNBOUND work items queued to a bound workqueue always run > locally. This is a good thing normally, but not when the user has
The constant name used there is a bit misleading but you can't put work items which are queued w/ queue_work() on foreign cpus by default. queue_work() has always guaranteed local execution. The problem is that workqueue can't currently tell whether a queue_work() user expects cpu locality for correctness or optimization. It'd be great if we introduce queue_work_on_local() or sth and replace correctness ones with it but that involves auditing each and every queue_work() usage. If anybody is up for the task, I'd be happy to help. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/