All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS & TrueCrypt - Speed Test
Date: Thu, 28 Jul 2011 09:20:50 -0400	[thread overview]
Message-ID: <4E316232.9090506@gmail.com> (raw)
In-Reply-To: <4E311257.1030109@redhat.com>

On 07/28/2011 03:40 AM, Milan Broz wrote:
> echo 3 > /proc/ss/cm/drop_caches
> 
> does the same in more controlled way

Hello Milan,

Arraign I didn't know that one.  Good to know!

> Can you use something more recent? There were huge changes.
> The same for user space.

I always stay with the stock kernel (Fedora 14) so I don't have to take
care of bug-fixes & security-updates for the kernel :)   ...but I'll try
to run a newer kernel If I do the test again.

> 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).

I had no idea it used dm-crypt!  That's great.

> 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 user space (and FUSE)  only for old
> containers and some magic for hidden container.

Great,  I'll do that.  I'll perform the tests again (everything equal:
kernel, disk, data, empty buffers, rsync) but I'll use xts this time for
LUKS.  I'll report back.

Thanks Milan!
Jorge

  reply	other threads:[~2011-07-28 13:20 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
2011-07-28 13:20   ` Jorge Fábregas [this message]
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=4E316232.9090506@gmail.com \
    --to=jorge.fabregas@gmail.com \
    --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.