hello, On 22/07/2009 Heinz Diehl wrote: > > instead there seem to be keyfile sizes which cryptsetup is able to > > process a lot faster than others. especially 128k seems to be a very > > good size for key files. > > > can anybody explain that to me? > > First: I'm not a LUKS/dmcrypt developer. > > Could it be that other processes have influenced your benchmarking, e.g. > by creating a little bit disk I/O? And what iteration time did you use? > If it's not specified with --iter-time, does LUKS use the same default for > all? i didn't specify the iteration, but a quick look at luksDump gives the impression that this should not be the reason: # cryptsetup luksDump /dev/vg_int/ctest2 | grep Iterations Iterations: 419928 Iterations: 421541 Iterations: 419581 Iterations: 423105 Iterations: 420162 Iterations: 421461 Iterations: 420988 Iterations: 421656 greetings, jonas
Attachment:
signature.asc
Description: Digital signature
