Michael Hampton wrote: > My first suspicion would be that Linux can't get any other I/O off the > disk when both kcryptd threads are tied up. It was only when one of the > two threads appeared in top that my music started playing again. Clearly > I have enough CPU to handle both reading and writing encrypted data at > once (it's only a 1.2GHz Intel Core 2 Duo). So perhaps only one thread > should be handling these sorts of sustained write operations, so that > the other thread can fetch my music off the disk? In kernel 2.6.24 is only one thread per crypt device processing writes. Any chance to test it with 2.6.24? I have some dm-crypt write congestion prevention patches, but it seems that not needed for 2.6.24... Milan -- mbroz@xxxxxxxxxx --------------------------------------------------------------------- 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
