> Il giorno 14 set 2017, alle ore 09:14, oleksa...@natalenko.name ha scritto:
>
> Tested-by: Oleksandr Natalenko
>
>> Similarly to CFQ, BFQ has its write-throttling heuristics, and it
>> is better not to combine them with further write-throttling
>> heuristics of a
> Il giorno 14 set 2017, alle ore 09:14, oleksa...@natalenko.name ha scritto:
>
> Tested-by: Oleksandr Natalenko
>
>> Similarly to CFQ, BFQ has its write-throttling heuristics, and it
>> is better not to combine them with further write-throttling
>> heuristics of a different nature.
>> So this
Tested-by: Oleksandr Natalenko
Similarly to CFQ, BFQ has its write-throttling heuristics, and it
is better not to combine them with further write-throttling
heuristics of a different nature.
So this commit disables write-back throttling for a device if BFQ
is used as
Tested-by: Oleksandr Natalenko
Similarly to CFQ, BFQ has its write-throttling heuristics, and it
is better not to combine them with further write-throttling
heuristics of a different nature.
So this commit disables write-back throttling for a device if BFQ
is used as I/O scheduler for that
Similarly to CFQ, BFQ has its write-throttling heuristics, and it
is better not to combine them with further write-throttling
heuristics of a different nature.
So this commit disables write-back throttling for a device if BFQ
is used as I/O scheduler for that device.
Signed-off-by: Luca Miccio
Similarly to CFQ, BFQ has its write-throttling heuristics, and it
is better not to combine them with further write-throttling
heuristics of a different nature.
So this commit disables write-back throttling for a device if BFQ
is used as I/O scheduler for that device.
Signed-off-by: Luca Miccio
6 matches
Mail list logo