DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: 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 23:33:54 +0200	[thread overview]
Message-ID: <4F7383C2.8040007@redhat.com> (raw)
In-Reply-To: <4F6BF806.1000504@holgerdanske.com>

On 03/23/2012 05:11 AM, David Christensen wrote:
> I have a 1.5 TB SATA hard drive I use for back-up's.  It has a single
> large partition encrypted with LUKS/ dm-crypt and formatted with ext4.
> I've noticed what appears to be single-threaded behavior when one
> process is performing a long-lived write to the disk (notably 'ssh
> user@host tar ...>  backupfile.tar.gz') and another process attempts to
> access the disk (either read or write).  This is tolerable for a back-up
> application, but would not be acceptable for multi-user, multi-process,
> and/or multi-threaded applications (file server, terminal server, web
> server, etc.).

You forgot to mention kernel version, it changed in various versions.

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.

Milan

  parent reply	other threads:[~2012-03-28 21:34 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 [this message]
2012-03-29  2:56   ` David Christensen

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=4F7383C2.8040007@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=dpchrist@holgerdanske.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox