From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932256Ab2IXUIP (ORCPT ); Mon, 24 Sep 2012 16:08:15 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:36814 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932180Ab2IXUIO (ORCPT ); Mon, 24 Sep 2012 16:08:14 -0400 Date: Mon, 24 Sep 2012 13:08:09 -0700 From: Tejun Heo To: Deepawali Verma Cc: Chinmay V S , Daniel Taylor , anish singh , "linux-kernel@vger.kernel.org" Subject: Re: Work queue questions Message-ID: <20120924200809.GC29689@google.com> References: <5A9BC72FD5CEC94EA024CED8E31D701A4C572F72@wdscexmb03.sc.wdc.com> <5A9BC72FD5CEC94EA024CED8E31D701A4C572FAE@wdscexmb03.sc.wdc.com> <20120924181025.GG7694@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Mon, Sep 24, 2012 at 08:57:40PM +0100, Deepawali Verma wrote: > May be I misunderstood, I read in the documentation about max_active. > In this case, max_active is 1, but I created three workqueues, do you I see. Why are you doing that? Is there ordering requirement? Why not just use system_unbound_wq? > mean to say for this case, single thread can process three requests > queued up in the three different workqueues. In the following execution log you posted, kworker/u:1-21 [000] 110.964895: task_event: MYTASKJOB2381 XStarted kworker/u:1-21 [000] 110.964909: task_event: MYTASKJOB2381 Xstopped kworker/u:1-21 [000] 110.965137: task_event: MYTASKJOB2382 XStarted kworker/u:1-21 [000] 110.965154: task_event: MYTASKJOB2382 Xstopped kworker/u:5-3724 [000] 110.965311: task_event: MYTASKJOB2383 XStarted kworker/u:5-3724 [000] 110.965325: task_event: MYTASKJOB2383 Xstopped The first two got executed on the same worker thread but the third one is on a different one. It really looks like you just don't have large enough work for scheduler to interleave them or migrate workers to different CPUs. Thanks. -- tejun