linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Deepawali Verma <dverma249@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Chinmay V S <cvs268@gmail.com>,
	Daniel Taylor <Daniel.Taylor@wdc.com>,
	anish singh <anish198519851985@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Work queue questions
Date: Mon, 24 Sep 2012 20:57:40 +0100	[thread overview]
Message-ID: <CAHCeSFr4stF6BNGL7=7oPYzKqOZ-Ya8VUD02rjFRq1thMULFXw@mail.gmail.com> (raw)
In-Reply-To: <20120924181025.GG7694@google.com>

Hi Tejun,

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
mean to say for this case, single thread can process three requests
queued up in the three different workqueues.

Sorry, if I misunderstood.

Regards,
Deepa



On Mon, Sep 24, 2012 at 7:10 PM, Tejun Heo <tj@kernel.org> wrote:
> On Mon, Sep 24, 2012 at 05:56:10PM +0100, Deepawali Verma wrote:
>> Hi,
>>
>> This is sample code snippet as I cannot post my project code. In
>> reality here, this work handler is copying the big chunks of data that
>> code is
>>  here in my driver. This is running on quad core cortex A9 Thats why I
>> asked. If there are 4 cpu cores, then there must be parallelism. Now
>> Tajun, what do you say?
>
> My name is Tejun and please lose the frigging attitude when you're
> asking things.
>
>> >>> alloc_workqueue(obj[i].my_obj_wq_name,WQ_UNBOUND,1);
>
> Especially if you're not properly reading any of the documentation,
> function comment and my explicit response mentioning @max_active. :(
>
> --
> tejun

  reply	other threads:[~2012-09-24 19:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 17:35 Work queue questions Dinky Verma
2012-09-21 17:49 ` Tejun Heo
2012-09-21 18:30   ` Deepawali Verma
2012-09-21 18:35     ` Tejun Heo
2012-09-21 19:26       ` Deepawali Verma
2012-09-21 19:27         ` Tejun Heo
2012-09-21 19:35           ` Deepawali Verma
2012-09-21 19:40             ` Tejun Heo
2012-09-22  4:24             ` anish singh
2012-09-22  5:27               ` Daniel Taylor
2012-09-22  6:05                 ` anish singh
2012-09-22  6:12                   ` Tejun Heo
2012-09-22  6:18                   ` Daniel Taylor
2012-09-24  7:25                     ` Deepawali Verma
     [not found]                       ` <CAK-9PRB7KvPNgcsXiNG08-7OdrkkNc2ushusXh9rVm93J0xcHA@mail.gmail.com>
     [not found]                         ` <CAHCeSFqmeOkKySxMUXgtnev+HL-NC6MdmeuDYONymYaNczb7RA@mail.gmail.com>
2012-09-24 16:56                           ` Deepawali Verma
2012-09-24 18:10                             ` Tejun Heo
2012-09-24 19:57                               ` Deepawali Verma [this message]
2012-09-24 20:08                                 ` Tejun Heo
2012-09-24 20:52                                   ` Deepawali Verma
2012-09-24 20:54                                     ` Tejun Heo
2012-09-25  3:05                                   ` anish singh
2012-09-24 17:07                           ` Chinmay V S

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHCeSFr4stF6BNGL7=7oPYzKqOZ-Ya8VUD02rjFRq1thMULFXw@mail.gmail.com' \
    --to=dverma249@gmail.com \
    --cc=Daniel.Taylor@wdc.com \
    --cc=anish198519851985@gmail.com \
    --cc=cvs268@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).