On Thu, Oct 01 2009, Mike Galbraith wrote: > > CIC_SEEK_THR is 8K jiffies so that would be 8seconds on 1000HZ system. Try > > using one "slice_idle" period of 8 ms. But it might turn out to be too > > short depending on the disk speed. > > Yeah, it is too short, as is even _400_ ms. Trouble is, by the time > some new task is determined to be seeky, the damage is already done. > > The below does better, though not as well as "just say no to overload" > of course ;-) So this essentially takes the "avoid impact from previous slice" to a new extreme, but idling even before dispatching requests from the new queue. We basically do two things to prevent this already - one is to only set the slice when the first request is actually serviced, and the other is to drain async requests completely before starting sync ones. I'm a bit surprised that the former doesn't solve the problem fully, I guess what happens is that if the drive has been flooded with writes, it may service the new read immediately and then return to finish emptying its writeback cache. This will cause an impact for any sync IO until that cache is flushed, and then cause that sync queue to not get as much service as it should have. Perhaps the "set slice on first complete" isn't working correctly? Or perhaps we just need to be more extreme. -- Jens Axboe -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
