On Tue, 11 Apr 2017 11:38:27 +0200, Jan Kara wrote:
> when testing my fix for 0-day reports with writeback throttling I came
> across somewhat unexpected behavior with user interface of writeback
> throttling. So currently if CFQ is used as an IO scheduler, we disable
> writeback throttling
Hi,
when testing my fix for 0-day reports with writeback throttling I came
across somewhat unexpected behavior with user interface of writeback
throttling. So currently if CFQ is used as an IO scheduler, we disable
writeback throttling because they don't go well together. However when user
has
