Re: workqueue thing

Tejun Heo
2009-12-23T03:43:13Z

On 12/22/2009 08:03 PM, Peter Zijlstra wrote:
> On Tue, 2009-12-22 at 08:50 +0900, Tejun Heo wrote:
>>> But as it stands I don't think its wise to replace the current workqueue
>>> implementation with this, esp since there are known heavy CPU users
>>> using it, nor have you addressed the queueing issue (or is that the
>>> restoration of the single-queue workqueue?)
>>
>> The queueing one is addressed and which CPU-heavy users are you
>> talking about? Workqueues have always been CPU-affine. Not much
>> changes for its users by cmwq.
>
> crypto for one (no clue what other bits we have atm, there might be some
> async raid-n helper bits too, or whatever).

This one is being discussed in a different thread.

> And yes that does change, the current design ensures we don't run more
> than one crypto job per cpu, whereas with your stuff that can be
> arbitrary many per cpu (up to some artificial limit of 127 or so).

Nope, with max_active set to 1 the behavior will remain exactly the
same as the current workqueues and as I've described in the head
message and the patch description, there now is no global limit only
max_active limits apply. It got solved together with the singlethread
thing.

Thanks.

--
tejun