[PATCH 12/14] nvme: utilize two queue maps, one for reads and one for writes

NVMe does round-robin between queues by default, which means that sharing a queue map for both reads and writes can be problematic in terms of read servicing. It's much easier to flood the queue with writes and reduce the read servicing. Implement two queue maps, one for reads and one for writes.

Re: [PATCH 12/14] nvme: utilize two queue maps, one for reads and one for writes

On 10/25/18 11:16 PM, Jens Axboe wrote: NVMe does round-robin between queues by default, which means that sharing a queue map for both reads and writes can be problematic in terms of read servicing. It's much easier to flood the queue with writes and reduce the read servicing. Implement two queu

[PATCH 12/14] nvme: utilize two queue maps, one for reads and one for writes

NVMe does round-robin between queues by default, which means that sharing a queue map for both reads and writes can be problematic in terms of read servicing. It's much easier to flood the queue with writes and reduce the read servicing. Implement two queue maps, one for reads and one for writes.