> AFAIK Nested dm-crypt is not extreme for some folk who have routine > configurations using it. But if in_interrupt is set how does this code > work for them now compared to how it worked before? Previously they will all pile up on the single worker thread. Now in the nested case the nested work is run in their own context. This should actually scale better because you get parallelism too, not contention on a single resource. The only difference to the non nested case is that the wq is not used. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
