[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] cmwq and dm-crypt devices?
- 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: [dm-devel] cmwq and dm-crypt devices?
- Date: Wed, 3 Nov 2010 13:33:47 +0100
> 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.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]