> It's not about needing per-cpu binding but if works can be executed on > the same cpu they were issued, it's almost always beneficial. The > only reason why we have single threaded workqueue now is to limit the > number of threads. That would argue very strongly for putting all the logic in one place so everything shares queues. > > Only if you make the default assumed max wait time for the work too low - > > its a tunable behaviour in fact. > > If the default workqueue is made to manage concurrency well, most > works should be able to just use it, so the queue will contain both > long running ones and short running ones which can disturb the current > batch like processing of the default workqueue which is assumed to > have only short ones. Not sure why it matters - the short ones will instead end up being processed serially in parallel to the hog. > kthreads). It would be great if a single work API is exported and > concurrency is managed automatically so that no one else has to worry > about concurrency but achieving that requires much more intelligence > on the workqueue implementation as the basic concurrency policies > which used to be imposed by those segregations need to be handled > automatically. Maybe it's better trade-off to leave those > segregations as-are and just add another workqueue type with dynamic > thread pool. The more intelligence in the workqueue logic, the less in the drivers and the more it can be adjusted and adapt itself. Consider things like power management which might argue for breaking the cpu affinity to avoid waking up a sleeping CPU in preference to jumping work between processors -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
