From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Reconsidering default options for cryptsetup-reencrypt
Date: Fri, 23 Nov 2012 07:07:20 +0100 [thread overview]
Message-ID: <20121123060720.GA5520@tansi.org> (raw)
In-Reply-To: <50AEF7B3.4000807@babioch.de>
On Fri, Nov 23, 2012 at 05:12:35AM +0100, Karol Babioch wrote:
> Hi,
>
> I'm currently reencrypting my (hardware) RAID setup, which is quite big
> (12 TB) in order to change the cipher from aes-xts-plain to aes-xts-plain64.
>
> While playing around with various options, I found out that a block size
> of 64 MB and the use of direct I/O results in the highest speed for me.
This seems to be RAID options (i.e. out-of-scope for cryptsetup), and
very specific ones as you have some hardware RAID solution. Also 64MB
block size is very, very large and will be a problem for some workloads.
Also, your sped gain of 10% is negligible, as it is likely not robust
and very much dependent on the workload.
[...]
> Maybe I'm just generalizing too much here when trying
> to come up with some conclusions based on my hardware.
I think you do. I also think that HW raid is a bit exotic on Linux
these days, as SW RAID gives better features and often better
performance.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-11-23 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 4:12 [dm-crypt] Reconsidering default options for cryptsetup-reencrypt Karol Babioch
2012-11-23 6:07 ` Arno Wagner [this message]
2012-11-23 9:00 ` Milan Broz
2012-11-23 9:27 ` Arno Wagner
2012-11-23 9:42 ` Milan Broz
2012-11-24 17:01 ` Sven Eschenberg
2012-11-24 20:59 ` Milan Broz
2012-12-03 0:27 ` DarKRaveR
2012-11-23 8:49 ` Milan Broz
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=20121123060720.GA5520@tansi.org \
--to=arno@wagner.name \
--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.