From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: slowness when cp respectively send/receiving on top of dm-crypt
Date: Sat, 28 Nov 2015 19:38:56 +0100 [thread overview]
Message-ID: <1448735936.31687.1.camel@scientia.net> (raw)
In-Reply-To: <CAJCQCtQZ0-q5m=DM5nsrveU-W=Bc-L75m+Oyx6XsYHs2pJwzCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Sat, 2015-11-28 at 11:34 -0700, Chris Murphy wrote:
> It sounds to me like maybe LUKS is configured to use an encryption
> algorithm that isn't subject to CPU optimized support, e.g. aes-xts
> on
> my laptop gets 1600MiB/s where serpent-cbc gets only 68MiB/s and pegs
> the CPU. This is reported by 'cryptsetup benchmark'
hmmm...
$ /sbin/cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 910222 iterations per second
PBKDF2-sha256 590414 iterations per second
PBKDF2-sha512 399609 iterations per second
PBKDF2-ripemd160 548418 iterations per second
PBKDF2-whirlpool 179060 iterations per second
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 474,3 MiB/s 1686,2 MiB/s
serpent-cbc 128b 69,4 MiB/s 235,3 MiB/s
twofish-cbc 128b 144,5 MiB/s 271,6 MiB/s
aes-cbc 256b 348,0 MiB/s 1239,4 MiB/s
serpent-cbc 256b 68,8 MiB/s 231,5 MiB/s
twofish-cbc 256b 146,6 MiB/s 268,9 MiB/s
aes-xts 256b 1381,3 MiB/s 1384,3 MiB/s
serpent-xts 256b 238,6 MiB/s 231,1 MiB/s
twofish-xts 256b 262,9 MiB/s 266,7 MiB/s
aes-xts 512b 1085,7 MiB/s 1078,9 MiB/s
serpent-xts 512b 242,1 MiB/s 230,2 MiB/s
twofish-xts 512b 266,8 MiB/s 265,9 MiB/s
I'm having aes-xts-plain64 with 512 bit key...
that's still 1 GiB/s
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
next prev parent reply other threads:[~2015-11-28 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 17:03 slowness when cp respectively send/receiving on top of dm-crypt Christoph Anton Mitterer
2015-11-27 19:00 ` Henk Slager
2015-11-28 4:14 ` Christoph Anton Mitterer
2015-11-28 18:34 ` Chris Murphy
2015-11-28 18:38 ` Christoph Anton Mitterer [this message]
2015-11-28 18:55 ` Chris Murphy
2015-11-28 18:37 ` Henk Slager
2015-11-29 5:31 ` Duncan
2015-11-29 19:29 ` Henk Slager
2015-11-30 5:02 ` Duncan
2015-11-30 18:26 ` Henk Slager
2015-11-28 4:55 ` Christoph Anton Mitterer
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=1448735936.31687.1.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox