From: Matthias Schniedermeyer <ms@citd.de>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] unusual writing speeds when benchmark speeds are high enough
Date: Sun, 17 Mar 2013 23:55:16 +0100 [thread overview]
Message-ID: <20130317225516.GA6053@citd.de> (raw)
In-Reply-To: <CAFnMBaSjtk+qPOMR=7QH5rvPpWhGG9ba-QwhOExPR587LbRVZw@mail.gmail.com>
On 17.03.2013 17:36, .. ink .. wrote:
> Sorry for my previous email without a title,resending the email with a
> title this time.
>
> 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 <at> 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 <at> 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 <at> sheep 9] ~ > cryptsetup create test test.img
> Passsatz eingeben:
>
> [17.03.2013 21:51 Uhr]
> [root <at> 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 <at> 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.
dd was with conv=fsync?
Otherwise you are measuring buffer cache.
> Where is the wrong in his system? version of cryptsetup used is 1.6.0
I would say, there are quite a few details missing.
Hardware, Software?
28.4 MB/s also isn't what i would call fast, what is that?
--
Matthias
next prev parent reply other threads:[~2013-03-17 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 21:36 [dm-crypt] unusual writing speeds when benchmark speeds are high enough .. ink ..
2013-03-17 22:55 ` Matthias Schniedermeyer [this message]
2013-03-18 6:42 ` .. ink ..
2013-03-18 8:37 ` Matthias Schniedermeyer
2013-03-18 10:01 ` Heinz Diehl
2013-03-18 10:20 ` Arno Wagner
2013-03-18 10:43 ` Matthias Schniedermeyer
2013-03-17 23:07 ` Arno Wagner
2013-03-17 23:19 ` .. ink ..
2013-03-18 6:22 ` Milan Broz
2013-03-18 7:58 ` .. ink ..
2013-03-18 18:16 ` .. ink ..
2013-03-18 7:06 ` Heinz Diehl
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=20130317225516.GA6053@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
--cc=mhogomchungu@gmail.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 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.