From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chr Subject: Re: [dm-crypt] INFO: task mount:11202 blocked for more than 120 seconds Date: Mon, 17 Mar 2008 19:36:21 +0100 Message-ID: <200803171936.22260.chunkeey@web.de> References: <20080317173609.GD29322@agk.fab.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080317173609.GD29322@agk.fab.redhat.com> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: Alasdair G Kergon Cc: Christian Kujau , Milan Broz , David Chinner , LKML , xfs@oss.sgi.com, dm-devel@redhat.com, dm-crypt@saout.de, Herbert Xu , Ritesh Raj Sarraf List-Id: dm-devel.ids On Monday 17 March 2008 18:36:09 Alasdair G Kergon wrote: > Latest version for everyone to try: > > From: Milan Broz > > Fix regression in dm-crypt introduced in commit > 3a7f6c990ad04e6f576a159876c602d14d6f7fef > (dm crypt: use async crypto). > > If write requests need to be split into pieces, the code must not > process them in parallel because the crypto context cannot be shared. > So there can be parallel crypto operations on one part of the write, > but only one write bio can be processed at a time. > > This is not optimal and the workqueue code need to be optimized for > parallel processing, but for now it solves problem without affecting > the performance of synchronous crypto operation (most of current > dm-crypt users). > > Signed-off-by: Milan Broz > Signed-off-by: Alasdair G Kergon Tested-by: Christian Lamparter Well, the dm-crypt regressions seems to be gone. :) Thanks for your work & time! Regards, Christian