From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: cmwq and dm-crypt devices? Date: Wed, 3 Nov 2010 13:33:47 +0100 Message-ID: <20101103123347.GB18935@basil.fritz.box> References: <1271958538-11193-1-git-send-email-san@google.com> <4BD08F78.4000701@redhat.com> <4BD099DB.2020108@redhat.com> <20101102220207.GD23680@redhat.com> <4CD12F6E.8040501@kernel.org> <20101103115144.GA18935@basil.fritz.box> <4CD14DF1.90601@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4CD14DF1.90601@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Milan Broz Cc: Christophe Saout , Mike Snitzer , Brian Swetland , San Mehat , device-mapper development , Andi Kleen , Tejun Heo , Andrew Morton , Alasdair G Kergon List-Id: dm-devel.ids > 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.