From: Milan Broz <mbroz@redhat.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS performance penalty
Date: Sun, 01 May 2011 10:20:26 +0200 [thread overview]
Message-ID: <4DBD17CA.1020004@redhat.com> (raw)
In-Reply-To: <4DBC9D78.8070203@divisive.info>
On 05/01/2011 01:38 AM, michael dye wrote:
> I find that using LUKS results in a tremendous performance penalty:
> 156MB/s writes with LUKS v. 613MB/s without on a PCI-E SSD using ext4.
> Am I failing to set up LUKS correctly? What can I do to improve
> performance?
Please retest it with 2.6.38 kernel which uses per cpu encryption threads.
You should get better throughput on multicore systems
(with some real fs test using more threads, for one thread it will
be probably not much better, it run encryption on CPU core which
submitted it.)
Milan
prev parent reply other threads:[~2011-05-01 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 23:38 [dm-crypt] LUKS performance penalty michael dye
2011-05-01 8:20 ` Milan Broz [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=4DBD17CA.1020004@redhat.com \
--to=mbroz@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox