On Thu, Dec 1, 2016 at 10:30 AM, Jens Axboe <ax...@fb.com> wrote:
> It's two different kinds of throttling. The vm absolutely should
> throttle at dirty time, to avoid having insane amounts of memory dirty.
> On the block layer side, throttling is about avoid the device queues
> being too long. It's very similar to the buffer bloating on the
> networking side. The block layer throttling is not a fix for the vm
> allowing too much memory to be dirty and causing issues, it's about
> keeping the device response latencies in check.
Sure. But if we really do just end up blocking in the block layer (in
situations where we didn't used to), that may be a bad thing. It might
be better to feed that information back to the VM instead,
particularly for writes, where the VM layer already tries to ratelimit
And frankly, it's almost purely writes that matter. There just aren't
a lot of ways to get that many parallel reads in real life.
I haven't looked at your patches, so maybe you already do this.