> So, possibly no connection to dm-crypt, just the > buffer-cache having badly tuned parameters for > this type of operation. Quite possible. Normally the block devices kvm provides for guests are backed by the host's cache, which results in native I/O throughput (100MiB/s read and write on encrypted partitions) in the guests but has a major starvation problem when dm-crypt is part of the mix. Forcing kvm to go directly to the disks bypassing the host's cache (using drive=...,cache=none) fixes the starvation issue completely but limits throughput to an appaling 25MB/s read and 15MB/s write ... Any idea why this setup would behave as it does? How can I check if flushes really are the problem? Thanks, Chris _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
