> Loop is not ideal device to test but it is not the problem. > The main problem is that dm-crypt uses only one core per device. > If you want to do some tests, try this patch > http://lkml.org/lkml/2010/11/12/344 > (but there is still some issues and it will not help much > if only one process generates IOs.) I've tried to apply this patch against 2.6.36 and 2.6.37-rc2 but without success: # patch -p1 -i ./dm-crypt-patch.diff patching file drivers/md/dm-crypt.c Hunk #2 FAILED at 78. Hunk #3 succeeded at 91 with fuzz 2. Hunk #4 FAILED at 133. Hunk #5 FAILED at 152. Hunk #7 FAILED at 227. Hunk #8 FAILED at 239. Hunk #9 FAILED at 259. Hunk #10 FAILED at 336. Hunk #11 FAILED at 358. Hunk #12 FAILED at 381. Hunk #13 FAILED at 501. Hunk #14 FAILED at 546. Hunk #15 FAILED at 562. Hunk #16 succeeded at 574 with fuzz 2. Hunk #17 FAILED at 583. Hunk #19 succeeded at 1065 with fuzz 1. Hunk #20 FAILED at 1096. Hunk #21 FAILED at 1136. Hunk #22 FAILED at 1155. Hunk #23 FAILED at 1174. Hunk #24 FAILED at 1209. Hunk #25 FAILED at 1240. Hunk #26 FAILED at 1259. Hunk #27 FAILED at 1323. Hunk #28 FAILED at 1354. Hunk #29 FAILED at 1365. Hunk #30 FAILED at 1378. Hunk #31 FAILED at 1405. 25 out of 31 hunks FAILED -- saving rejects to file drivers/md/dm-crypt.c.rej What version of kernel should i patch? GIT? _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
