On Monday 17 March 2008 18:36:09 Alasdair G Kergon wrote: > Latest version for everyone to try: > > From: Milan Broz <mbroz@xxxxxxxxxx> > > 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 <mbroz@xxxxxxxxxx> > Signed-off-by: Alasdair G Kergon <agk@xxxxxxxxxx> Tested-by: Christian Lamparter <chunkeey@xxxxxx> Well, the dm-crypt regressions seems to be gone. :) Thanks for your work & time! Regards, Christian --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
