linux-kernel - Re: [dm-devel] DM-CRYPT: Scale to multiple CPUs v3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 Oct 2010 22:20:31 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Milan Broz <mbroz@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Mike Snitzer <snitzer@...hat.com>,
	Andi Kleen <ak@...ux.intel.com>,
	device-mapper development <dm-devel@...hat.com>,
	pedrib@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [dm-devel] DM-CRYPT: Scale to multiple CPUs v3

> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/