From: "shmick@riseup.net" <shmick@riseup.net>
To: christian@madez.de, dm-crypt@saout.de
Subject: Re: [dm-crypt] REQUIRED CIPHERS TEST takes 20 minutes each for aes-related ciphers
Date: Fri, 29 Nov 2013 01:30:09 +1100 [thread overview]
Message-ID: <52975371.3050404@riseup.net> (raw)
In-Reply-To: <b1bf0a8a357ca9ddcafcfeccdd4f1d6e@madez.de>
christian@madez.de:
> Hello,
>
> I just compiled cryptsetup-1.6.2 on a machine with AES-NI. During the
> compilation there were some tests. The lines of the output when the
> issue occurred were:
>
> REQUIRED CIPHERS TEST
> # Algorithm | Key | Encryption | Decryption
> aes-cbc 256b 975.0 MiB/s 2037065.0 MiB/s
> aes-lrw 384b 103909.0 MiB/s 158691.0 MiB/s
> aes-xts 512b 1731833.0 MiB/s 1681613.0 MiB/s
> twofish-cbc 256b 241.3 MiB/s 499.5 MiB/s
> twofish-lrw 384b 448.6 MiB/s 453.0 MiB/s
> twofish-xts 512b 497.0 MiB/s 496.0 MiB/s
> serpent-cbc 256b 108.5 MiB/s 351.3 MiB/s
> serpent-lrw 384b 333.7 MiB/s 333.0 MiB/s
> serpent-xts 512b 363.3 MiB/s 341.0 MiB/s
> blowfish-cbc 256b 129.6 MiB/s 500.5 MiB/s
> des3_ede-cbc 192b 34.3 MiB/s 35.4 MiB/s
> cast5-cbc 128b 121.9 MiB/s 474.0 MiB/s
when these tests ran did all cores process or just 1 single core ?
do you know if cryptsetup can take advantage of multi threading on multi
core processors ?
>
> The tests for aes-cbc, aes-lrw and aes-xts took very long (nearly one
> hour for all three combined) on a Intel Core i5-4670K. All other tests
> were finished in a few seconds.
>
> Is this wanted behavior?
>
> Best regards,
> Christian Weinz
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>
next prev parent reply other threads:[~2013-11-28 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 13:25 [dm-crypt] REQUIRED CIPHERS TEST takes 20 minutes each for aes-related ciphers christian
2013-11-28 14:30 ` shmick [this message]
2013-11-28 14:54 ` christian
2013-11-28 14:58 ` Milan Broz
2013-11-28 14:51 ` Milan Broz
2013-11-28 23:28 ` christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52975371.3050404@riseup.net \
--to=shmick@riseup.net \
--cc=christian@madez.de \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.