> AFAIK Nested dm-crypt is not extreme for some folk who have routine
quoted text
> 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@linux.intel.com -- Speaking for myself only.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/