On 04/07/2017 12:47 PM, Binoy Jayan wrote: > =============================================================================== > dm-crypt optimization for larger block sizes > =============================================================================== ... > Tests with dd [direct i/o] > > Sequential read -0.134 % > Sequential Write +0.091 % > > Tests with fio [Aggregate bandwidth - aggrb] > > Random Read +0.358 % > Random Write +0.010 % > > Tests with bonnie++ [768 MiB File, 384 MiB Ram] > after mounting dm-crypt target as ext4 > > Sequential o/p [per-char] -2.876 % > Sequential o/p [per-blk] +0.992 % > Sequential o/p [re-write] +4.465 % > > Sequential i/p [per-char] -0.453 % > Sequential i/p [per-blk] -0.740 % > > Sequential create -0.255 % > Sequential delete +0.042 % > Random create -0.007 % > Random delete +0.454 % > > NB: The '+' sign shows improvement and '-' shows degradation. > The tests were performed with minimal cpu load. > Tests with higher cpu load to be done Well, it is good that there is no performance degradation but it would be nice to have some user of it that proves it is really working for your hw. FYI - with patch that increases dmcrypt sector size to 4k I can see improvement in speed usually in 5-15% with sync AES-NI (depends on access pattern), with dmcrypt mapped to memory it is even close to 20% speed up (but such a configuration is completely artificial). I wonder why increased dmcrypt sector size does not work for your hw, it should help as well (and can be combiuned later with this IV approach). (For native 4k drives this should be used in future anyway...) Milan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
