Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 11 Mar 2011 19:30:02 +0100 (CET) Message-ID: <4D7A6A26.5000501@redhat.com> Date: Fri, 11 Mar 2011 19:29:58 +0100 From: Milan Broz MIME-Version: 1.0 References: <20110308164508.GA8729@darkside.kls.lan> <20110310165730.GC20504@alboin.amr.corp.intel.com> <20110310175411.GB25027@darkside.kls.lan> <20110311011842.GA5698@alboin.amr.corp.intel.com> <20110311180334.GA11382@darkside.kls.lan> In-Reply-To: <20110311180334.GA11382@darkside.kls.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mario 'BitKoenig' Holbe , Andi Kleen , dm-crypt@saout.de, linux-kernel@vger.kernel.org, Alasdair G Kergon On 03/11/2011 07:03 PM, Mario 'BitKoenig' Holbe wrote: >> You probably need to find some way >> to make pcrypt (parallel crypt layer) work for dmcrypt. That may >> actually give you more speedup too than your old hack because >> it can balance over more cores. dmcrypt is already using async crypto interface, it is ready for parallelization on this level. Perhaps the problem is that pcrypt is not yet implemented for needed algorithms? Milan