public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Mickler <florian@mickler.org>
To: Tejun Heo <tj@kernel.org>
Cc: Dave Chinner <david@fromorbit.com>,
	lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Christoph Lameter <cl@linux-foundation.org>
Subject: Re: [PATCH UPDATED] workqueue: add documentation
Date: Mon, 13 Sep 2010 10:16:43 +0200	[thread overview]
Message-ID: <20100913101643.22a1e7d5@schatten.dmk.lab> (raw)
In-Reply-To: <4C8DDBEC.3010900@kernel.org>


one more detail, seems like this never ends... sorry :) 

On Mon, 13 Sep 2010 10:08:12 +0200
Tejun Heo <tj@kernel.org> wrote:




> +
> +For an unbound wq, the above concurrency management doesn't apply and
> +the gcwq for the pseudo unbound CPU tries to start executing all work
> +items as soon as possible.  The responsibility of regulating
> +concurrency level is on the users.  There is also a flag to mark a
> +bound wq to ignore the concurrency management.  Please refer to the
> +Workqueue Attributes section for details.

renamed to "API section" 

regards,
Flo

  reply	other threads:[~2010-09-13  8:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 15:40 [PATCH] workqueue: add documentation Tejun Heo
2010-09-08 15:51 ` [PATCH UPDATED] " Tejun Heo
2010-09-09  8:02   ` Florian Mickler
2010-09-09 10:22     ` Tejun Heo
2010-09-09 18:50       ` Florian Mickler
2010-09-10 10:25         ` Tejun Heo
2010-09-10 14:26           ` Florian Mickler
2010-09-10 14:55             ` Tejun Heo
2010-09-10 17:43               ` Randy Dunlap
2010-09-12 10:50                 ` Tejun Heo
2010-09-13  0:51               ` Dave Chinner
2010-09-13  8:08                 ` Tejun Heo
2010-09-13  8:16                   ` Florian Mickler [this message]
2010-09-13  8:27                     ` Tejun Heo

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=20100913101643.22a1e7d5@schatten.dmk.lab \
    --to=florian@mickler.org \
    --cc=cl@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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