From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-crypto@vger.kernel.org
Subject: Re: [0/3] [DM] dm-crypt: Add async crypto support
Date: Wed, 11 Jul 2007 09:45:20 +0200 [thread overview]
Message-ID: <f721vl$h3i$1@sea.gmane.org> (raw)
In-Reply-To: 20070711030303.GA6730@gondor.apana.org.au
Herbert Xu wrote:
> I've rebased the async dm-crypt patches for 2.6.22. In doing
> so I've refactored the kcryptd split so that all crypto operations
> happen in kcryptd while all IO submissions occur in kcryptd-io.
will this reduce latencies and stalls with dm-crypt? When copying large
files dm-crypted machines (swap+root) are often not very usable.
Also in some cases I see no i/o happening in vmstat, sometimes for a minute,
while lots of processes are blocked waiting for data read and decrypted
from disk. But I don't have a recipe for reproducing this so far and only
tested up to 2.6.21.*.
Regards, Andreas
next prev parent reply other threads:[~2007-07-11 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 3:03 [0/3] [DM] dm-crypt: Add async crypto support Herbert Xu
2007-07-11 3:05 ` [PATCH 1/3] [DM] dm-crypt: Move post-processing into its own queue Herbert Xu
2007-07-25 9:45 ` Milan Broz
2007-07-11 3:05 ` [PATCH 2/3] [DM] dm-crypt: Add async infrastructure Herbert Xu
2007-07-11 3:05 ` [PATCH 3/3] [DM] dm-crypt: Use crypto ablkcipher interface Herbert Xu
2007-07-11 7:45 ` Andreas Jellinghaus [this message]
2007-07-25 9:23 ` [0/3] [DM] dm-crypt: Add async crypto support Herbert Xu
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='f721vl$h3i$1@sea.gmane.org' \
--to=aj@ciphirelabs.com \
--cc=linux-crypto@vger.kernel.org \
/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