public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ralf <ralf+gentoo@ramses-pyramidenbau.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cryptsetup wont use aes-xts:plain64
Date: Wed, 22 Apr 2015 09:46:43 +0200	[thread overview]
Message-ID: <553751E3.1000000@ramses-pyramidenbau.de> (raw)
In-Reply-To: <CAAD4mYhM30-b0aGcfqL_W-=veznwjkYEiQhwVGrHp7Ng2MVKPA@mail.gmail.com>

Just try `cryptsetup benchmark`

Cheers

On 04/22/2015 06:09 AM, R0b0t1 wrote:
> AES cipher algo (AES-NI) is the fastest if you have the necessary
> hardware. Twofish cipher algo (x86_64, 3-way parallel) is a close
> second, but will slow access down slightly. Serpent is also usably
> fast.
>
> CONFIG_CRYPTO_AES_NI_INTEL = ~200mb/s (limited by disk in my case)
> CONFIG_CRYPTO_TWOFISH_X86_64_3WAY = ~130mb/s
>
> `cryptsetup --cipher {twofish,aes}-xts-plain64 --key-size 512 --hash
> sha512 --iter-time 5000`
>



  reply	other threads:[~2015-04-22  7:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21  9:21 [gentoo-user] cryptsetup wont use aes-xts:plain64 Marko Weber | 8000
2015-04-21 10:54 ` Heiko Baums
2015-04-22  4:09 ` R0b0t1
2015-04-22  7:46   ` Ralf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-18 10:27 Marko Weber | 8000
2015-04-18 11:48 ` Ralf
2015-04-18 12:07 ` Heiko Baums
2015-04-18 12:12   ` Ralf
2015-04-18 12:44     ` Heiko Baums
2015-04-18 13:45       ` Ralf
2015-04-18 12:33 ` Heiko Baums
2015-04-18 15:41 ` Heiko Baums
2015-04-20 13:40   ` Marko Weber | 8000
2015-04-19  1:35 ` Fernando Rodriguez
2015-04-19  1:47   ` Fernando Rodriguez
2015-04-20 13:43   ` Marko Weber | 8000
2015-04-20 17:43     ` Heiko Baums
2015-04-20 13:59 ` Marko Weber | 8000
2015-04-20 16:19 ` bitlord

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=553751E3.1000000@ramses-pyramidenbau.de \
    --to=ralf+gentoo@ramses-pyramidenbau.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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