> Il giorno 12 lug 2017, alle ore 16:22, Jens Axboe ha
> scritto:
>
> On 07/12/2017 03:41 AM, Paolo Valente wrote:
>>
>>> Il giorno 11 lug 2017, alle ore 15:58, Hou Tao ha
>>> scritto:
>>>
>>> There are mq devices (eg., virtio-blk, nbd and loopback)
On 07/12/2017 03:41 AM, Paolo Valente wrote:
>
>> Il giorno 11 lug 2017, alle ore 15:58, Hou Tao ha
>> scritto:
>>
>> There are mq devices (eg., virtio-blk, nbd and loopback) which don't
>> invoke blk_mq_run_hw_queues() after the completion of a request.
>> If bfq is enabled
On 2017/7/12 17:41, Paolo Valente wrote:
>
>> Il giorno 11 lug 2017, alle ore 15:58, Hou Tao ha
>> scritto:
>>
>> There are mq devices (eg., virtio-blk, nbd and loopback) which don't
>> invoke blk_mq_run_hw_queues() after the completion of a request.
>> If bfq is enabled
> Il giorno 11 lug 2017, alle ore 15:58, Hou Tao ha
> scritto:
>
> There are mq devices (eg., virtio-blk, nbd and loopback) which don't
> invoke blk_mq_run_hw_queues() after the completion of a request.
> If bfq is enabled on these devices and the slice_idle attribute or
>
There are mq devices (eg., virtio-blk, nbd and loopback) which don't
invoke blk_mq_run_hw_queues() after the completion of a request.
If bfq is enabled on these devices and the slice_idle attribute or
strict_guarantees attribute is set as zero, it is possible that
after a request completion the