On Thu, Sep 27, 2012 at 01:20:42AM +0800, Lai Jiangshan wrote: > works in system_long_wq will be running long. > add WQ_CPU_INTENSIVE to system_long_wq to avoid these kinds of works occupy > the running wokers which delay the normal works. > > if system_long_wq is designed for only sleep-long works, not running-long > works, > this patch makes no sense.
There "long" doesn't mean it's gonna consume a lot of CPU cycles, so it should contribute to concurrency management. The plan is to remove system_long_wq once we got rid of flushing of system_wq via flush_scheduled_work() and directly through flush_workqueue(). I think we're pretty close, so let's not add more usage of it. 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/
