All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Roche <Tom_Roche@pobox.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] cryptsetup benchmark with I/O?
Date: Sat, 22 Mar 2014 01:51:26 -0400	[thread overview]
Message-ID: <877g7mpyqp.fsf@pobox.com> (raw)


summary: Is there an I/O-inclusive cryptsetup benchmark available for users?

details:

Thanks to PePa's script, which I have fiddled[1], it is now quite easy/fast to install LMDE[2] with LUKS and LVM2. So easy that I'd like to improve (if not optimize) my cryptsetup, if it's not too difficult/time-consuming. On my target hardware (which is a few years old)

$ sudo cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1       313569 iterations per second
> PBKDF2-sha256     190511 iterations per second
> PBKDF2-sha512     125068 iterations per second
> PBKDF2-ripemd160  254015 iterations per second
> PBKDF2-whirlpool  132663 iterations per second
> #  Algorithm | Key |  Encryption |  Decryption
>      aes-cbc   128b   142.2 MiB/s   164.7 MiB/s
>  serpent-cbc   128b    54.5 MiB/s   225.8 MiB/s
>  twofish-cbc   128b   131.6 MiB/s   180.0 MiB/s
>      aes-cbc   256b   113.8 MiB/s   125.5 MiB/s
>  serpent-cbc   256b    55.7 MiB/s   224.2 MiB/s
>  twofish-cbc   256b   133.2 MiB/s   180.9 MiB/s
>      aes-xts   256b   168.0 MiB/s   165.0 MiB/s
>  serpent-xts   256b   197.6 MiB/s   201.5 MiB/s
>  twofish-xts   256b   168.3 MiB/s   170.0 MiB/s
>      aes-xts   512b   126.4 MiB/s   126.4 MiB/s
>  serpent-xts   512b   195.5 MiB/s   197.8 MiB/s
>  twofish-xts   512b   167.0 MiB/s   167.0 MiB/s

But, as it says in the first line, `cryptsetup benchmark` tests memory but not I/O. So although my current selection (--cipher=serpent-xts-plain64 , --key-size=256) seems to be working OK, I'd like to know, ...

Is there a better benchmark? with I/O? Ideally, I'd like an automated test I could let run for not too long (a few hours, tops) to more realistically check my current selection against "the standard" (which, IIUC, is --cipher=aes-xts-plain64 , --key-size=512). I don't have data on the target hardware, and the script makes it easy/quick to blast the old partitions/volumes and twiddle the crypto, so I could do that for an interation or two before I "setup the box for real."

TIA, Tom Roche <Tom_Roche@pobox.com>

[1]: https://bitbucket.org/tlroche/install_resizable_encrypted_lmde
[2]: http://www.linuxmint.com/download_lmde.php

             reply	other threads:[~2014-03-22  5:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22  5:51 Tom Roche [this message]
2014-03-22  7:40 ` [dm-crypt] cryptsetup benchmark with I/O? Arno Wagner

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=877g7mpyqp.fsf@pobox.com \
    --to=tom_roche@pobox.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.