On Fri, Nov 27, 2015 at 9:14 PM, Christoph Anton Mitterer <cales...@scientia.net> wrote:
> - Bust most importantly,... if the reason was SMR, why should always > when no IO happens dmcrypt_write be at basically full CPU. It sounds to me like maybe LUKS is configured to use an encryption algorithm that isn't subject to CPU optimized support, e.g. aes-xts on my laptop gets 1600MiB/s where serpent-cbc gets only 68MiB/s and pegs the CPU. This is reported by 'cryptsetup benchmark' -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
