[dm-devel] max_sectors_kb limitations with VDO and dm-thin

Ryan Norwood ryan.p.norwood at gmail.com
Fri Apr 19 14:40:19 UTC 2019


We have been using dm-thin layered above VDO and have noticed that our
performance is not optimal for large sequential writes as max_sectors_kb
and max_hw_sectors_kb for all thin devices are set to 4k due to the VDO
layer beneath.

This effectively eliminates the performance optimizations for sequential
writes to skip both zeroing and COW overhead when a write fully overlaps a
thin chunk as all bios are split into 4k which always be less than the 64k
thin chunk minimum.

Is this known behavior? Is there any way around this issue?

We are using RHEL 7.5 with kernel 3.10.0-862.20.2.el7.x86_64.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/dm-devel/attachments/20190419/26a721e6/attachment.htm>


More information about the dm-devel mailing list