From: David Christensen <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS/ dm-crypt/ ext4 appears to be single threaded
Date: Thu, 22 Mar 2012 21:11:50 -0700 [thread overview]
Message-ID: <4F6BF806.1000504@holgerdanske.com> (raw)
dm-crypt:
Thread moved from debian-user.
Please comment.
TIA,
David
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.).
Is this a fundamental limitation of LUKS, dm-crypt, and/or ext4, or
something I've configured/ misconfigured?
If a fundamental limitation, is there something I can substitute to
eliminate the problem?
Some manufacturers make hard drives with built-in encryption. Are these
supported by Debian, Linux, or BSD?
http://www.seagate.com/www/en-us/products/self-encrypting-drives/
Any other comments or suggestions?
TIA,
David
next reply other threads:[~2012-03-23 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 4:11 David Christensen [this message]
2012-03-26 13:51 ` [dm-crypt] LUKS/ dm-crypt/ ext4 appears to be single threaded Roscoe
2012-03-28 21:33 ` Milan Broz
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=4F6BF806.1000504@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox