Re: blk-mq merge flags

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/15/2016 09:08 AM, Christoph Hellwig wrote:
Jens, Keith -

any comments?  I think the lack of BLK_MQ_F_SG_MERGE for nvme
is rather harmful at the moment, as I get much better request
packing with it.  I'd rather fix this in the block layer, but
if that's not ok I can also send a pure NVMe patch.

We can default to merging, and have drivers opt out, if they need to. NVMe is probably the only one that doesn't set the flag currently, so the net effect of the two different approaches would be the same. We'll have a slightly higher CPU overhead without a perf win for workloads that don't get merging, but overall it's always a win if we can merge commands. So a better default, I think, even for nvme.

--
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-block" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux