DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Romain Francoise <romain@orebokech.com>
Cc: dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Switch to XTS mode for LUKS in cryptsetup in 1.6.0 (Was Re: [ANNOUNCE] cryptsetup 1.6.0-rc1)
Date: Fri, 04 Jan 2013 20:14:42 +0100	[thread overview]
Message-ID: <50E72A22.3060007@gmail.com> (raw)
In-Reply-To: <87sj6gn5g7.fsf@silenus.orebokech.com>

On 01/04/2013 07:55 PM, Romain Francoise wrote:
> Milan Broz <gmazyland@gmail.com> writes:
> 
>> Any serious objections to not do that now?
> 
> How does it compare to cbc in terms of (real-world) performance?

It is slower but on recent systems it shouldn't not be bottleneck
(even with fast storage).

I really prefer security to performance here.

But anyway, there is now benchmark command to test it.

An example (on my 3 year old Thinkpad x201 notebook with AES-NI):

# Tests are approximate using memory only (no storage IO).
#  Algorithm | Key |  Encryption |  Decryption
     aes-cbc   128b   789.0 MiB/s  1899.0 MiB/s
     aes-cbc   256b   595.0 MiB/s  1445.0 MiB/s
     aes-xts   256b   572.0 MiB/s   571.4 MiB/s
     aes-xts   512b   465.0 MiB/s   467.0 MiB/s

(I think XTS got some more optimization in recent kernel, this is from 3.6.)

You can try it yourself, just run "cryptsetup benchmark" with 1.6.0-rc1,
perhaps we will need some new FAQ entry here.

Milan

 

  reply	other threads:[~2013-01-04 19:14 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
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 [this message]
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=50E72A22.3060007@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=romain@orebokech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox