From: ".. ink .." <mhogomchungu@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] (no subject)
Date: Sun, 17 Mar 2013 17:30:34 -0400 [thread overview]
Message-ID: <CAFnMBaSphRNVYu_QM55bn1fWAOyr8RC+Zk1jK5m2ZeuikwK8Ug@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
A user of cryptsetup(through zuluCrypt) asked me a question i can not
answer and asking it here.
In his system,"cryptsetup benchmark" gives the following results:
[root@sheep 13] ~ > cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1 341333 iterations per second
PBKDF2-sha256 193607 iterations per second
PBKDF2-sha512 64125 iterations per second
PBKDF2-ripemd160 303758 iterations per second
PBKDF2-whirlpool 64125 iterations per second
# Algorithm | Key | Encryption | Decryption
aes-cbc 128b 183,6 MiB/s 215,4 MiB/s
serpent-cbc 128b 68,0 MiB/s 68,9 MiB/s
twofish-cbc 128b 167,7 MiB/s 177,5 MiB/s
aes-cbc 256b 142,3 MiB/s 161,5 MiB/s
serpent-cbc 256b 69,7 MiB/s 67,0 MiB/s
twofish-cbc 256b 170,1 MiB/s 177,8 MiB/s
aes-xts 256b 201,2 MiB/s 205,6 MiB/s
serpent-xts 256b 69,7 MiB/s 67,6 MiB/s
twofish-xts 256b 180,5 MiB/s 175,6 MiB/s
aes-xts 512b 147,0 MiB/s 152,5 MiB/s
serpent-xts 512b 70,5 MiB/s 67,8 MiB/s
twofish-xts 512b 182,0 MiB/s 176,0 MiB/s
The system is decent enought.
The write speed he is getting though through the mapper is unusually
slow,the test is below:
[root@sheep 8] ~ > dd if=/dev/zero of=test.img bs=70M count=1
1+0 Datensätze ein
1+0 Datensätze aus
73400320 Bytes (73 MB) kopiert, 2,58497 s, 28,4 MB/s
[17.03.2013 21:50 Uhr]
[root@sheep 9] ~ > cryptsetup create test test.img
Passsatz eingeben:
[17.03.2013 21:51 Uhr]
[root@sheep 10] ~ > dd if=/dev/zero of=/dev/mapper/test bs=10M count=1
1+0 Datensätze ein
1+0 Datensätze aus
10485760 Bytes (10 MB) kopiert, 67,2014 s, 156 kB/s
[17.03.2013 21:52 Uhr]
[root@sheep 11] ~ > cryptsetup remove test
As the test show,He is getting 156kB/s when using dd over the encryption
mapper verses 28MB/s when using dd straight.
Where is the wrong in his system? version of cryptsetup used is 1.6.0
[-- Attachment #2: Type: text/html, Size: 2201 bytes --]
next reply other threads:[~2013-03-17 21:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 21:30 .. ink .. [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-29 17:48 [dm-crypt] (no subject) Hammad Siddiqi
2017-04-29 18:30 ` Arno Wagner
2017-04-29 19:19 ` Hammad Siddiqi
2017-05-01 17:37 ` Hammad Siddiqi
2017-05-01 18:45 ` Michael Kjörling
2017-05-01 21:01 ` Arno Wagner
2017-05-02 0:29 ` Diagon
2017-05-02 20:49 ` Arno Wagner
2016-06-18 21:40 RAS RAS
2016-06-20 7:52 ` Milan Broz
[not found] ` <1466423154.44272313@f313.i.mail.ru>
2016-06-20 12:02 ` Milan Broz
2015-05-04 14:50 janemba
2015-05-04 16:41 ` Arno Wagner
2014-02-07 13:51 Redwood Hyd
2012-12-29 22:22 .. ink ..
2012-12-29 22:46 ` Milan Broz
2012-12-29 23:15 ` .. ink ..
2012-12-29 23:39 ` Milan Broz
2012-12-29 23:53 ` .. ink ..
2012-12-30 7:12 ` .. ink ..
2012-12-30 9:05 ` Milan Broz
2012-12-30 9:19 ` .. ink ..
2012-12-30 10:51 ` Milan Broz
2012-12-30 11:49 ` .. ink ..
2012-10-10 21:11 ffrizzy
2012-10-10 21:09 ffrizzy
2012-10-10 23:13 ` Claudio Moretti
2012-10-09 6:24 ffrizzy
2012-10-09 6:21 ffrizzy
2012-09-04 1:20 Anil
2012-09-04 1:29 ` Arno Wagner
2011-09-18 10:58 Ingo Schmitt
2011-03-09 2:04 Rookcifer
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=CAFnMBaSphRNVYu_QM55bn1fWAOyr8RC+Zk1jK5m2ZeuikwK8Ug@mail.gmail.com \
--to=mhogomchungu@gmail.com \
--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.