From mboxrd@z Thu Jan 1 00:00:00 1970 From: Milan Broz Subject: Re: cmwq and dm-crypt devices? Date: Wed, 03 Nov 2010 12:56:33 +0100 Message-ID: <4CD14DF1.90601@redhat.com> 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> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20101103115144.GA18935@basil.fritz.box> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Andi Kleen Cc: Christophe Saout , Mike Snitzer , Brian Swetland , San Mehat , device-mapper development , Tejun Heo , Andrew Morton , Alasdair G Kergon List-Id: dm-devel.ids On 11/03/2010 12:51 PM, Andi Kleen wrote: >> >>> 2) scale up the number of workqueue threads used for a single dm-crypt >>> device so that a device can realize per-cpu concurrency (to address >>> Andi's scalability concerns: https://patchwork.kernel.org/patch/244031/) > > They are already addressed in my patchkit and the patches seem to be used > by more and more users. It's just you guys who are behind. No, sorry, they are not addressed. Did you read my mail with tests? http://lkml.org/lkml/2010/10/20/215 Async crypto is not solved at all by your patch. Milan