[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: Milan Broz <mbroz redhat com>
- Cc: Andi Kleen <ak linux intel com>, Mike Snitzer <snitzer redhat com>, linux-kernel vger kernel org, device-mapper development <dm-devel redhat com>, Andi Kleen <andi firstfloor org>, pedrib gmail com
- Subject: Re: [dm-devel] DM-CRYPT: Scale to multiple CPUs v3
- Date: Sun, 10 Oct 2010 22:20:31 +0200
> But previously, there were threads per device, so if one IO thread blocks,
> others stacked mappings can continue
> Now I see possibility for deadlock there because we have one io thread now
> (assuming that 1 CPU situation Alasdair mentioned).
That path calls the crypto worker thread, not the IO worker thread?
crypto worker should be fine here, only IO worker would be a problem
I think because crypto doesn't really block on nested IO.
-Andi
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]