[dm-crypt] dm-crypt multithreaded yet?
htd at fancy-poultry.org
Sun Dec 16 22:29:38 CET 2012
On 16.12.2012, Milan Broz wrote:
> My suggestion is that using AES-NI extension helps much more with
> the current upstream code than anything else (for AES, obviously).
And not to forget the optimized modules in the kernel.
Here's an example with a WD Black Caviar using serpent
encryption on a test machine.
This is stock cryptsetup. Wouldn't have had more speed
[htd at test2 ~]$ cat /proc/cpuinfo
model name : Intel(R) Core(TM) i5 CPU M 450 @ 2.40GHz
[root at test2 ~]# hdparm -i /dev/sda | grep Model
Model=WDC WD7500BPKT-00PK4T0, FwRev=01.01A01,
[root at test2 ~]# cryptsetup luksDump /dev/sda1
LUKS header information for /dev/sda1
Cipher name: serpent
Cipher mode: xts-plain64:whirlpool
Hash spec: whirlpool
Payload offset: 4096
MK bits: 512
[root at test2 mapper]# hdparm -t /dev/mapper/luks-xxxxxxxxx
Timing buffered disk reads: 386 MB in 3.01 seconds = 128.27 MB/sec
serpent_sse2_x86_64 50364 6
serpent_generic 25563 1 serpent_sse2_x86_64
lrw 13145 1 serpent_sse2_x86_64
glue_helper 13172 1 serpent_sse2_x86_64
ablk_helper 13269 1 serpent_sse2_x86_64
xts 12871 1 serpent_sse2_x86_64
gf128mul 14333 2 lrw,xts
dm_crypt 22893 3
More information about the dm-crypt