[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] DM-CRYPT: Scale to multiple CPUs v3
- From: Andi Kleen <andi firstfloor org>
- To: Andi Kleen <andi firstfloor org>, Milan Broz <mbroz redhat com>, Mike Snitzer <snitzer redhat com>, Andi Kleen <ak linux intel com>, device-mapper development <dm-devel redhat com>, pedrib gmail com, linux-kernel vger kernel org
- Subject: Re: [dm-devel] DM-CRYPT: Scale to multiple CPUs v3
- Date: Sun, 10 Oct 2010 20:51:00 +0200
> 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 linux intel com -- Speaking for myself only.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]