public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/2 V2] workqueue: use dedicated creater kthread for all pools
Date: Tue, 29 Jul 2014 11:04:59 -0400	[thread overview]
Message-ID: <20140729150459.GE4791@htj.dyndns.org> (raw)
In-Reply-To: <1406625376-19177-1-git-send-email-laijs@cn.fujitsu.com>

Hello,

On Tue, Jul 29, 2014 at 05:16:07PM +0800, Lai Jiangshan wrote:

First of all, the patch is too big.  This is a rather pervasive
change.  Please split it up if at all possible.

> +/* Start the mayday timer and the creater when needed */
> +static inline void start_creater_work(struct worker_pool *pool)
> +{
> +	if (pool->nr_idle || pool->creating || list_empty(&pool->worklist))
> +		return;

pool->creating is an optimization around queue_kthread_work(), right?
So that you don't have to grab the lock every time a work item is
queued.  Please explain things like that explicitly.  Also, the
condition itself needs explanation.  This is what guarantees that the
queue is not stalled after all.

Hmmm... list_empty() is unnecessary when called from the queueing
path.  Do we want to move that out of this function?

>  	/* we own @work, set data and link */
>  	set_work_pwq(work, pwq, extra_flags);
>  	list_add_tail(&work->entry, head);
> +	start_creater_work(pool);

creator is spelled with an 'o' not 'e'.  Also, it'd be better if the
name reflects that this is a kthread_work not a workqueue one.

> +static void create_worker(struct kthread_work *work)
>  {
...
>  fail:
>  	if (id >= 0)
>  		ida_simple_remove(&pool->worker_ida, id);
>  	kfree(worker);
> -	return NULL;
> +
> +	/* cool down before next create_worker() */
> +	schedule_timeout_interruptible(CREATE_COOLDOWN);
> +	del_timer_sync(&pool->mayday_timer);
> +
> +	spin_lock_irq(&pool->lock);
> +	pool->creating = false;
> +	start_creater_work(pool);
> +	spin_unlock_irq(&pool->lock);

Why?  Just sleep and retry?  What's the point of requeueing?

> -/**
>   * process_one_work - process single work
>   * @worker: self
>   * @work: work to process
> @@ -1991,6 +1905,7 @@ __acquires(&pool->lock)
>  	work_color = get_work_color(work);
>  
>  	list_del_init(&work->entry);
> +	start_creater_work(pool);

Should this be combined with wake_up_worker()?

Thanks.

-- 
tejun

  reply	other threads:[~2014-07-29 15:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26  3:04 [PATCH 0/3] workqueue: offload the worker-management out from kworker Lai Jiangshan
2014-07-26  3:04 ` [PATCH 1/3] workqueue: migrate the new worker before add it to idle_list Lai Jiangshan
2014-07-26  3:04 ` [PATCH 2/3] workqueue: use dedicated creater kthread for all pools Lai Jiangshan
2014-07-28 18:55   ` Tejun Heo
2014-07-29  1:26     ` Lai Jiangshan
2014-07-29  2:16       ` Tejun Heo
2014-07-29  9:16         ` [PATCH RFC 2/2 V2] " Lai Jiangshan
2014-07-29 15:04           ` Tejun Heo [this message]
2014-07-30  0:32             ` Lai Jiangshan
2014-07-30  3:23               ` Tejun Heo
2014-07-30  3:46                 ` Lai Jiangshan
2014-07-30  3:46                   ` Tejun Heo
2014-07-26  3:04 ` [PATCH 3/3] workqueue: cleanup may_start_working() Lai Jiangshan

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=20140729150459.GE4791@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.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