On Fri, May 1, 2015 at 6:17 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Fri, May 01, 2015 at 11:28:01AM +0800, Ming Lei wrote: >> If there are too many pending per work I/O, too many >> high priority work thread can be generated so that >> system performance can be effected. >> >> This patch limits the max pending per work I/O as 16, >> and will fackback to single queue mode when the max >> number is reached. > > Why would you do this fall back? Shouldn't we just communicate > a concurrency limit to the workqueue code? It can't work with workqueue's concurrency limit because the queue is shared by all loop block devices, and the limit is on the whole queue. That was also the test I asked Justin to run, and looks it doesn't work. Thanks, Ming Lei -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html