From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 18 Aug 2010 16:36:30 +0200 (CEST) Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o7IEaSth028407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 18 Aug 2010 10:36:29 -0400 Received: from [10.34.26.53] (tawny.brq.redhat.com [10.34.26.53]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o7IEaRwC012176 for ; Wed, 18 Aug 2010 10:36:28 -0400 Message-ID: <4C6BEFEB.8050209@redhat.com> Date: Wed, 18 Aug 2010 16:36:27 +0200 From: Milan Broz MIME-Version: 1.0 References: <20100817184635.GA17921@tansi.org> <4C6BC751.10506@redhat.com> <20100818131826.GA12428@fancy-poultry.org> In-Reply-To: <20100818131826.GA12428@fancy-poultry.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] dm-crypt flush-to-disk freezes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 08/18/2010 03:18 PM, Heinz Diehl wrote: > On 18.08.2010, Milan Broz wrote: > >> btw I hope that in 2.6.36 we switch to global workqueues >> per cpu for dm-crypt, unfortunately Alasdair is still waiting >> with committing it (patches are ready and I am using it myself). >> (It can help or it can make it worse here. It needs testing.) > > Where can I get these patches? Not yet in upstream dm tree still... So my working version is temporarily here http://mbroz.fedorapeople.org/dm-crypt/ It basically patch from Andi Kleen with some minor fixes, split into 4 parts for easy review. (You have to apply _always_ all 4 patches.) Version for 2.6.34/35 is split into one file (actually I am using this version on my stable machine now). Probably this is what you want. Please note one thing - it creates threads per CPU, but work submitted by one cpu should never be processed by other thread. So it helps if you have parallel application but will not help too much if all work is committed from one process. More discussion - see dm-devel archive. Milan