Herbert Xu wrote: > I've rebased the async dm-crypt patches for 2.6.22. In doing > so I've refactored the kcryptd split so that all crypto operations > happen in kcryptd while all IO submissions occur in kcryptd-io.
will this reduce latencies and stalls with dm-crypt? When copying large files dm-crypted machines (swap+root) are often not very usable. Also in some cases I see no i/o happening in vmstat, sometimes for a minute, while lots of processes are blocked waiting for data read and decrypted from disk. But I don't have a recipe for reproducing this so far and only tested up to 2.6.21.*. Regards, Andreas - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
