All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1
Date: Sun, 30 Dec 2012 00:15:15 +0100	[thread overview]
Message-ID: <20121229231515.GA6503@citd.de> (raw)
In-Reply-To: <50DF635C.90003@gmail.com>

On 29.12.2012 22:40, Milan Broz wrote:
> 
>    EXAMPLE:
>      # cryptsetup benchmark
>      # Tests are approximate using memory only (no storage IO).
>      PBKDF2-sha1       111077 iterations per second
>      PBKDF2-sha256      53718 iterations per second
>      PBKDF2-sha512      18832 iterations per second
>      PBKDF2-ripemd160   89775 iterations per second
>      PBKDF2-whirlpool   23918 iterations per second
>      #  Algorithm | Key | Encryption | Decryption
>           aes-cbc   128b  212.0 MiB/s  428.0 MiB/s
>       serpent-cbc   128b   23.1 MiB/s   66.0 MiB/s
>       twofish-cbc   128b   46.1 MiB/s   50.5 MiB/s
>           aes-cbc   256b  163.0 MiB/s  350.0 MiB/s
>       serpent-cbc   256b   23.1 MiB/s   66.0 MiB/s
>       twofish-cbc   256b   47.0 MiB/s   50.0 MiB/s
>           aes-xts   256b  190.0 MiB/s  190.0 MiB/s
>       serpent-xts   256b   58.4 MiB/s   58.0 MiB/s
>       twofish-xts   256b   49.0 MiB/s   49.5 MiB/s
>           aes-xts   512b  175.0 MiB/s  175.0 MiB/s
>       serpent-xts   512b   59.0 MiB/s   58.0 MiB/s
>       twofish-xts   512b   48.5 MiB/s   49.5 MiB/s
> 
>      (Note for example AES-NI decryption optimization effect in example above.)

Are you sure (about AES-NI)?
I get slightly higher values:

Tested with a self-compiled vanilla 3.7.1 kernel.

Core i7 3770 (Ivy Bridge), 4 cores, HT, no overclocking:
PBKDF2-sha1       393609 iterations per second
PBKDF2-sha256     257003 iterations per second
PBKDF2-sha512      91915 iterations per second
PBKDF2-ripemd160  386073 iterations per second
PBKDF2-whirlpool  154748 iterations per second
#  Algorithm | Key | Encryption | Decryption
     aes-cbc   128b  671.0 MiB/s  2483.0 MiB/s
 serpent-cbc   128b   98.3 MiB/s  320.4 MiB/s
 twofish-cbc   128b  205.0 MiB/s  377.6 MiB/s
     aes-cbc   256b  492.0 MiB/s  1816.0 MiB/s
 serpent-cbc   256b   98.3 MiB/s  319.4 MiB/s
 twofish-cbc   256b  204.4 MiB/s  375.6 MiB/s
     aes-xts   256b  1237.0 MiB/s  1252.0 MiB/s
 serpent-xts   256b  306.7 MiB/s  291.4 MiB/s
 twofish-xts   256b  336.7 MiB/s  338.3 MiB/s
     aes-xts   512b  1065.0 MiB/s  1076.0 MiB/s
 serpent-xts   512b  309.4 MiB/s  293.0 MiB/s
 twofish-xts   512b  336.7 MiB/s  337.7 MiB/s

Even my 2.5 years old low-spec first-generation (for AES-NI) machine 
gets slightly better results:
Core i5 650 (Westmere/Clarkdale), 2 cores, no HT, no overlocking:
PBKDF2-sha1       299251 iterations per second
PBKDF2-sha256     175229 iterations per second
PBKDF2-sha512      58409 iterations per second
PBKDF2-ripemd160  283705 iterations per second
PBKDF2-whirlpool   94568 iterations per second
#  Algorithm | Key | Encryption | Decryption
     aes-cbc   128b  711.3 MiB/s  1749.0 MiB/s
 serpent-cbc   128b   67.6 MiB/s  282.7 MiB/s
 twofish-cbc   128b  165.2 MiB/s  227.8 MiB/s
     aes-cbc   256b  540.0 MiB/s  1340.0 MiB/s
 serpent-cbc   256b   68.0 MiB/s  283.4 MiB/s
 twofish-cbc   256b  165.8 MiB/s  227.8 MiB/s
     aes-xts   256b  957.0 MiB/s  952.0 MiB/s
 serpent-xts   256b  243.8 MiB/s  258.0 MiB/s
 twofish-xts   256b  207.8 MiB/s  207.2 MiB/s
     aes-xts   512b  832.2 MiB/s  835.0 MiB/s
 serpent-xts   512b  243.3 MiB/s  257.2 MiB/s
 twofish-xts   512b  208.2 MiB/s  206.8 MiB/s







-- 

Matthias

  parent reply	other threads:[~2012-12-29 23:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29 21:40 [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1 Milan Broz
2012-12-29 22:24 ` Matthias Schniedermeyer
2012-12-29 22:42   ` Milan Broz
2012-12-29 23:21     ` Matthias Schniedermeyer
2012-12-29 23:15 ` Matthias Schniedermeyer [this message]
2012-12-29 23:31   ` Milan Broz
2013-01-02 12:50     ` Matthias Schniedermeyer
2013-01-02 20:55       ` Milan Broz
2012-12-30  8:38 ` Arno Wagner
2012-12-30  8:56   ` Sven Eschenberg
2012-12-30 10:20     ` Arno Wagner
2012-12-30 11:40       ` Milan Broz
2013-01-06 12:16         ` Yves-Alexis Perez
2013-01-06 16:24           ` Milan Broz
2013-01-07  6:23             ` Yves-Alexis Perez
2013-01-07  8:53               ` Milan Broz
2013-01-07 11:21               ` Sven Eschenberg
2013-01-07 18:12                 ` Milan Broz
2013-01-07 19:20                   ` Sven Eschenberg
2013-01-21 21:01                 ` Yves-Alexis Perez
2012-12-30 11:47       ` Milan Broz
2013-01-05 19:47         ` Jonas Meurer
2012-12-30  9:03   ` Milan Broz
2013-01-04 11:50 ` [dm-crypt] Switch to XTS mode for LUKS in cryptsetup in 1.6.0 (Was Re: [ANNOUNCE] cryptsetup 1.6.0-rc1) Milan Broz
2013-01-04 11:53   ` Ralf Ramsauer
2013-01-04 12:18     ` Milan Broz
2013-01-04 16:26       ` Arno Wagner
2013-01-04 20:20         ` Heinz Diehl
2013-01-04 20:56           ` Milan Broz
2013-01-04 22:05             ` Arno Wagner
2013-01-04 22:39               ` Milan Broz
2013-01-05 17:20                 ` Arno Wagner
2013-01-05 18:25                   ` Milan Broz
2013-01-05 19:47                     ` Arno Wagner
2013-01-04 13:39   ` Christoph Anton Mitterer
2013-01-04 16:17   ` Arno Wagner
2013-01-04 17:36   ` Zdenek Kaspar
2013-01-04 18:55   ` Romain Francoise
2013-01-04 19:14     ` Milan Broz
2013-01-04 21:56       ` 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=20121229231515.GA6503@citd.de \
    --to=ms@citd.de \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@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.