From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] workqueue: async worker destruction
Date: Tue, 18 Feb 2014 09:39:00 +0800 [thread overview]
Message-ID: <5302B9B4.9030808@cn.fujitsu.com> (raw)
In-Reply-To: <1392654243-2829-1-git-send-email-laijs@cn.fujitsu.com>
Sorry, the cover letter was forgotten to send to LKML.
On 02/18/2014 12:24 AM, Lai Jiangshan wrote:
> This patchset moves the worker-destruction(partial) to worker_thread(),
> and worker to be die will perform self-destruction.
>
> This async worker destruction helps us to reduce the mananger's invocation,
> and simply the idle-worker-timeout handler.
>
> This patchset requires earlier patch
> "workqueue: ensure @task is valid across kthread_stop()".
>
> Lai Jiangshan (3):
> workqueue: free worker earlier in worker_thread()
> workqueue: async worker destruction
> workqueue: kick worker to die directly in idle timeout handler
>
> kernel/workqueue.c | 135 +++++++++++++++++++---------------------------------
> 1 files changed, 49 insertions(+), 86 deletions(-)
>
next prev parent reply other threads:[~2014-02-18 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 14:02 [PATCH] workqueue: ensure @task is valid across kthread_stop() Lai Jiangshan
[not found] ` <1392654243-2829-1-git-send-email-laijs@cn.fujitsu.com>
2014-02-17 16:24 ` [PATCH 1/3] workqueue: free worker earlier in worker_thread() Lai Jiangshan
2014-02-17 16:24 ` [PATCH 2/3] workqueue: async worker destruction Lai Jiangshan
2014-02-18 22:29 ` Tejun Heo
2014-02-17 16:24 ` [PATCH 3/3] workqueue: kick worker to die directly in idle timeout handler Lai Jiangshan
2014-02-18 22:31 ` Tejun Heo
2014-02-18 1:39 ` Lai Jiangshan [this message]
2014-02-18 21:37 ` [PATCH wq/for-3.14-fixes] workqueue: ensure @task is valid across kthread_stop() Tejun Heo
2014-02-19 3:39 ` Lai Jiangshan
2014-02-19 3:39 ` Lai Jiangshan
2014-02-20 0:13 ` 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=5302B9B4.9030808@cn.fujitsu.com \
--to=laijs@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.