From: Andi Kleen <andi@firstfloor.org>
To: Milan Broz <mbroz@redhat.com>
Cc: Christophe Saout <christophe@saout.de>,
Mike Snitzer <snitzer@redhat.com>,
Brian Swetland <swetland@google.com>, San Mehat <san@google.com>,
device-mapper development <dm-devel@redhat.com>,
Andi Kleen <andi@firstfloor.org>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: cmwq and dm-crypt devices?
Date: Wed, 3 Nov 2010 13:33:47 +0100 [thread overview]
Message-ID: <20101103123347.GB18935@basil.fritz.box> (raw)
In-Reply-To: <4CD14DF1.90601@redhat.com>
> Async crypto is not solved at all by your patch.
You mean async crypto with 10 stacked devices? Find me a single
user who does that.
Traditionally stacking didn't work very
well in the kernel due to the limited kernel stack overflows.
I don't think that's significantly different here.
Anyways stacking could be probably fixed, but it's also that 99.999999%
of all dm-crypt users don't stack or use async but simply need a
scalable dm-crypt. Extreme stacking is extremly low on the
priority list.
Right now dm-crypt seems to have other problems anyways that need
to be addressed first.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-11-03 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 17:48 [PATCH] md: dm-crypt: Add option to re-use a new global work-queue San Mehat
2010-04-22 18:03 ` Milan Broz
2010-04-22 18:08 ` San Mehat
2010-04-22 18:47 ` Milan Broz
2010-04-22 19:42 ` San Mehat
2010-04-23 14:01 ` Heinz Mauelshagen
2010-04-27 20:58 ` San Mehat
2010-11-02 22:02 ` cmwq and dm-crypt devices? (was: Re: md: dm-crypt: Add option to re-use a new global work-queue.) Mike Snitzer
2010-11-03 9:46 ` cmwq and dm-crypt devices? Tejun Heo
2010-11-03 11:51 ` Andi Kleen
2010-11-03 11:56 ` Milan Broz
2010-11-03 12:33 ` Andi Kleen [this message]
2010-11-03 13:02 ` Milan Broz
2010-11-03 13:18 ` Alasdair G Kergon
2010-11-03 16:13 ` Andi Kleen
2010-11-03 16:17 ` Tejun Heo
2010-11-03 16:22 ` Milan Broz
2010-11-04 9:55 ` Andi Kleen
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=20101103123347.GB18935@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe@saout.de \
--cc=dm-devel@redhat.com \
--cc=mbroz@redhat.com \
--cc=san@google.com \
--cc=snitzer@redhat.com \
--cc=swetland@google.com \
--cc=tj@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 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.