From: David Christensen <dpchrist@holgerdanske.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS/ dm-crypt/ ext4 appears to be single threaded
Date: Wed, 28 Mar 2012 19:56:06 -0700 [thread overview]
Message-ID: <4F73CF46.500@holgerdanske.com> (raw)
In-Reply-To: <4F7383C2.8040007@redhat.com>
On 03/28/2012 02:33 PM, Milan Broz wrote:
Thank you for your reply. :-)
I've been trying to pay more attention, and it appears that the blocking
is limited to directories (and their subdirectories) where long-lived
writes are occurring (?). Am I understanding the issue correctly? Has
anyone else seen this?
Is "New Methods in Hard Disk Encryption" still relevant?
http://clemens.endorphin.org/cryptography
> You forgot to mention kernel version, it changed in various versions.
$ uname -a
Linux p43400e 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686
GNU/Linux
$ sudo cryptsetup --version
cryptsetup 1.1.3
$ cat /etc/debian_version
6.0.4
Are there any tunable parameters, options, alternatives, etc., that I
can adjust/ change to improve parallelism with what I have?
> For recent kernel 3.x, if multiple processes access the encrypted disk,
> it tries to keep submitted work on cpu which submitted it (so it run in
> parallel).
> There are some patches to change parallel operations to another model
> in dmcrypt, if you want to experiment, see
> http://people.redhat.com/mpatocka/patches/kernel/dm-crypt-paralelizace/current/
> I have several performance tests, and some of these patches perhaps
> appear in 3.5 kernel but it need still more work.
My kernel skills are far too rusty, and I need stability/ finished
product. So, I'll have to wait for those patches to get into Debian
stable (or testing).
David
prev parent reply other threads:[~2012-03-29 3:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 4:11 [dm-crypt] LUKS/ dm-crypt/ ext4 appears to be single threaded David Christensen
2012-03-26 13:51 ` Roscoe
2012-03-28 21:33 ` Milan Broz
2012-03-29 2:56 ` David Christensen [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=4F73CF46.500@holgerdanske.com \
--to=dpchrist@holgerdanske.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.