[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] cmwq and dm-crypt devices?
- From: Milan Broz <mbroz redhat com>
- To: Tejun Heo <tj kernel org>
- Cc: Christophe Saout <christophe saout de>, Mike Snitzer <snitzer redhat com>, Brian Swetland <swetland google com>, San Mehat <san google com>, device-mapper development <dm-devel redhat com>, Andi Kleen <andi firstfloor org>, Andrew Morton <akpm linux-foundation org>, Alasdair G Kergon <agk redhat com>
- Subject: Re: [dm-devel] cmwq and dm-crypt devices?
- Date: Wed, 03 Nov 2010 17:22:07 +0100
On 11/03/2010 05:17 PM, Tejun Heo wrote:
>> The old stacking relies on per device threads. Per device threads
>> cannot be combined with per CPU threads, because that would lead
>> to a thread explosion for large device counts.
>
> Dunno the context here but creating WQ_NON_REENTRANT | WQ_MEM_RECLAIM
> workqueue per device should achieve what you want. It will be per-cpu
> while reserving only one worker per workqueue, so there won't be
> explosion of threads.
Thanks for answer,
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?
Milan
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]