From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 9 Mar 2011 17:58:11 +0100 (CET) Date: Wed, 9 Mar 2011 17:58:35 +0100 From: Heinz Diehl Message-ID: <20110309165835.GA7855@fancy-poultry.org> References: <20110308164508.GA8729@darkside.kls.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110308164508.GA8729@darkside.kls.lan> 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: dm-crypt@saout.de On 09.03.2011, Mario 'BitKoenig' Holbe wrote: > dm-crypt in 2.6.38 changed to per-CPU workqueues to increase it's > performance by parallelizing encryption to multiple CPUs. > This modification seems to cause (massive) performance drops for > multiple parallel dm-crypt instances... Not that it adresses your problem, but in my case, this patch is the best one in the last months. On my good old primary LUKS/dmcrypt encrypted partitions, on an AMD Quadcore, it boosts performance from 45 MB/s w/o the patch up to 87 MB/s with it. That's just an incredibly huge performance boost.