From: Milan Broz <mbroz@redhat.com>
To: "Jorge Fábregas" <jorge.fabregas@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS & TrueCrypt - Speed Test
Date: Thu, 28 Jul 2011 09:40:07 +0200 [thread overview]
Message-ID: <4E311257.1030109@redhat.com> (raw)
In-Reply-To: <4E309CC0.6010706@gmail.com>
On 07/28/2011 01:18 AM, Jorge Fábregas wrote:
> - Between the above tests, I shut down the machine (to flush filesystem
> cache).
echo 3 > /proc/sys/vm/drop_caches
does the same in more controlled way
> - my system kernel: 2.6.35.13-92.fc14.i686
Can you use something more recent? There were huge changes.
The same for userspace.
BTW do you know that TC7 uses dm-crypt as backend? So with the same
mode and alignemnt you should get the same results
(except chained ciphers in TC).
> As you can see, there's almost a 4 minute difference. I was expecting
> LUKS to be faster (as dm-crypt is a kernel module) and TrueCrypt runs
> mainly in user space isn't it? Do you think the cipher operation modes
> (XTS vs CBC) played a role in this difference? Have any of you performed
> a similar test?
Perhaps because you tested different modes... Use the same mode
in cryptsetup
cryptstup luksFormat -c aes-xts-plain64 -s 512 ...
I would really wonder if speed differs, TC7 uses dmsetup to configure
dm-crypt mapping on Linux :-) It uses userspace (and FUSE) only for old
containers and some magic for hidden container.
Milan
next prev parent reply other threads:[~2011-07-28 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:18 [dm-crypt] LUKS & TrueCrypt - Speed Test Jorge Fábregas
2011-07-28 5:11 ` Arno Wagner
2011-07-28 13:07 ` Jorge Fábregas
2011-07-28 7:40 ` Milan Broz [this message]
2011-07-28 13:20 ` Jorge Fábregas
2011-07-28 23:58 ` Jorge Fábregas
2011-07-29 5:20 ` Arno Wagner
2011-07-29 9:52 ` Roscoe
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=4E311257.1030109@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=jorge.fabregas@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.