From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: cmwq and dm-crypt devices? Date: Thu, 4 Nov 2010 10:55:25 +0100 Message-ID: <20101104095525.GB32383@basil.fritz.box> References: <20101102220207.GD23680@redhat.com> <4CD12F6E.8040501@kernel.org> <20101103115144.GA18935@basil.fritz.box> <4CD14DF1.90601@redhat.com> <20101103123347.GB18935@basil.fritz.box> <20101103131835.GB5833@agk-dp.fab.redhat.com> <20101103161327.GC18935@basil.fritz.box> <4CD18B24.2010602@kernel.org> <4CD18C2F.2070408@redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4CD18C2F.2070408@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Milan Broz Cc: Christophe Saout , Mike Snitzer , Brian Swetland , San Mehat , device-mapper development , Andi Kleen , Tejun Heo , Andrew Morton , Alasdair G Kergon List-Id: dm-devel.ids > Yes, that is exactly what I was looking for but was not sure if possible. > > So switch to normal per device device threads (not singlethreaded as now) > combined with the Andi's fixes and it should work for everyone? Sounds like it could handle this. You'll need to revert some of the hunks in my patch, I ripped out some of the per device work queue code. It should not be very hard. -Andi -- ak@linux.intel.com -- Speaking for myself only.