From: Yves-Alexis Perez <corsac@debian.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Questions about LUKS / LVM
Date: Wed, 21 Sep 2011 10:39:09 -0700 [thread overview]
Message-ID: <1316626753.23302.4.camel@scapa> (raw)
In-Reply-To: <4E7769C7.5040805@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On lun., 2011-09-19 at 18:11 +0200, Quentin Lefebvre wrote:
> > It all depends, but generally no because cpu is _so_ much
> > faster than disk these days.
>
> Indeed, you won't notice it on a modern computer, especially for every
> day use. It may be painful for data transfer from one encrypted disk
> to
> another encrypted disk, but you can expect very good rates anyway. It
> depends on the cipher you use, on your machine, ...
>
Using a modern intel cpu with aesni helps a lot too.
Regards,
--
Yves-Alexis
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-09-21 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 15:45 [dm-crypt] Questions about LUKS / LVM Robbie Smith
2011-09-19 16:00 ` Karl O. Pinc
2011-09-19 16:11 ` Quentin Lefebvre
2011-09-21 17:39 ` Yves-Alexis Perez [this message]
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=1316626753.23302.4.camel@scapa \
--to=corsac@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox