Hi Milan,
I do agree, that this should be handled in userspace (as lvm does i.e.)
- unfortunately the luks Metadata cannot be updated easily in some
cases, an additional option for each 'unlock' call seems cumbersome,
thus I did ask about dmcrypt itself.
I do appreciate your effort on the patch, thanks!
Regards
-Sven
Milan Broz schrieb:
Sven Eschenberg wrote:
Dear List,
is there any convenient way to set a dm-crypts volume readahead value?
Cryptsetup and the luks metadata seem to lack this option. If one puts a
dm-crypt volume on a raid, aside from aligning it, the crypted volumes
readahead should match the stripe size.
Why does dmcrypt itself not evaluate the current readahead of the
underlying blockdevice and after creating the mapping applies it to the
newly created blockdevice?
Because the calculation of readahead should be done in userspace and cryptsetup
do not implement it yet. (Readahead setting was not available in old libdevmapper.)
---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
