LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: NeilBrown <neilb@suse.de>, Jan Kara <jack@suse.cz>,
Dongsu Park <dongsu.park@profitbricks.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH - v3?] workqueue: allow rescuer thread to do more work.
Date: Thu, 4 Dec 2014 09:01:50 +0800 [thread overview]
Message-ID: <547FB27E.5030904@cn.fujitsu.com> (raw)
In-Reply-To: <20141203180241.GD5013@htj.dyndns.org>
On 12/04/2014 02:02 AM, Tejun Heo wrote:
> So, something like the following. Only compile tested. I'll test it
> and post proper patches w/ due credits.
>
> Thanks.
>
> Index: work/kernel/workqueue.c
> ===================================================================
> --- work.orig/kernel/workqueue.c
> +++ work/kernel/workqueue.c
> @@ -1804,8 +1804,8 @@ static void pool_mayday_timeout(unsigned
> struct worker_pool *pool = (void *)__pool;
> struct work_struct *work;
>
> - spin_lock_irq(&wq_mayday_lock); /* for wq->maydays */
> - spin_lock(&pool->lock);
> + spin_lock_irq(&pool->lock);
> + spin_lock(&wq_mayday_lock); /* for wq->maydays */
>
> if (need_to_create_worker(pool)) {
> /*
> @@ -1818,8 +1818,8 @@ static void pool_mayday_timeout(unsigned
> send_mayday(work);
> }
>
> - spin_unlock(&pool->lock);
> - spin_unlock_irq(&wq_mayday_lock);
> + spin_unlock(&wq_mayday_lock);
> + spin_unlock_irq(&pool->lock);
>
> mod_timer(&pool->mayday_timer, jiffies + MAYDAY_INTERVAL);
> }
> @@ -2248,12 +2248,29 @@ repeat:
> * Slurp in all works issued via this workqueue and
> * process'em.
> */
> - WARN_ON_ONCE(!list_empty(&rescuer->scheduled));
> + WARN_ON_ONCE(!list_empty(scheduled));
> list_for_each_entry_safe(work, n, &pool->worklist, entry)
> if (get_work_pwq(work) == pwq)
> move_linked_works(work, scheduled, &n);
>
> - process_scheduled_works(rescuer);
> + if (!list_empty(scheduled)) {
> + process_scheduled_works(rescuer);
> +
> + /*
> + * The above execution of rescued work items could
> + * have created more to rescue through
> + * pwq_activate_first_delayed() or chained
> + * queueing. Let's put @pwq back on mayday list so
> + * that such back-to-back work items, which may be
> + * being used to relieve memory pressure, don't
> + * incur MAYDAY_INTERVAL delay inbetween.
> + */
> + if (need_to_create_worker(pool)) {
> + spin_lock(&wq_mayday_lock);
> + list_move_tail(&pwq->mayday_node, &wq->maydays);
how about the pwq is empty now? and ...
> + spin_unlock(&wq_mayday_lock);
> + }
> + }
>
> /*
> * Put the reference grabbed by send_mayday(). @pool won't
and the pwq is scheduled free here>
>
next prev parent reply other threads:[~2014-12-04 0:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 6:26 [PATCH/RFC] " NeilBrown
2014-10-29 14:32 ` Tejun Heo
2014-10-29 23:19 ` NeilBrown
2014-11-04 14:22 ` Tejun Heo
2014-11-06 16:58 ` Dongsu Park
2014-11-07 3:03 ` Lai Jiangshan
2014-11-10 5:28 ` NeilBrown
2014-11-10 8:52 ` Jan Kara
2014-11-10 22:04 ` NeilBrown
2014-11-14 17:21 ` Tejun Heo
2014-11-18 4:27 ` [PATCH - v3?] " NeilBrown
2014-11-18 6:01 ` Lai Jiangshan
2014-11-18 6:11 ` NeilBrown
2014-12-02 20:43 ` Tejun Heo
2014-12-03 0:40 ` NeilBrown
2014-12-03 17:20 ` Tejun Heo
2014-12-03 18:02 ` Tejun Heo
2014-12-03 22:31 ` Dongsu Park
2014-12-04 1:19 ` NeilBrown
2014-12-04 1:01 ` Lai Jiangshan [this message]
2014-12-04 14:57 ` Tejun Heo
2014-12-04 15:11 ` [PATCH workqueue/for-3.18-fixes 1/2] workqueue: invert the order between pool->lock and wq_mayday_lock Tejun Heo
2014-12-04 15:12 ` [PATCH workqueue/for-3.18-fixes 2/2] workqueue: allow rescuer thread to do more work Tejun Heo
2014-12-08 17:40 ` Tejun Heo
2014-12-08 22:47 ` NeilBrown
2014-12-05 2:09 ` [PATCH workqueue/for-3.18-fixes 1/2] workqueue: invert the order between pool->lock and wq_mayday_lock 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=547FB27E.5030904@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=dongsu.park@profitbricks.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tj@kernel.org \
--subject='Re: [PATCH - v3?] workqueue: allow rescuer thread to do more work.' \
/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
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).