From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: clear workers of a pool after the CPU is offline
Date: Fri, 26 Jul 2013 11:47:04 +0800 [thread overview]
Message-ID: <51F1F138.2060902@cn.fujitsu.com> (raw)
In-Reply-To: <20130726030711.GA30195@mtj.dyndns.org>
On 07/26/2013 11:07 AM, Tejun Heo wrote:
> Hello,
>
> On Fri, Jul 26, 2013 at 10:13:25AM +0800, Lai Jiangshan wrote:
>>> Hmmm... if I'm not confused, now the cpu pools just behave like a
>>> normal unbound pool when the cpu goes down,
>>
>> cpu pools are always referenced, they don't behave like unbound pool.
>
> Yeah sure, they don't get destroyed but pool management functions the
> same.
>
>>> which means that the idle
>>> cpu workers will exit once idle timeout is reached, right?
>>
>> No, no code to force the cpu workers quit currently.
>> you can just offline a cpu to see what happened to the workers.
>
> Hmmm? The idle timer thing doesn't work? Why?
>
any worker can't kill itself.
managers always tries to leave 2 workers.
so the workers of the offline cpu pool can't be totally destroyed.
(In old days, we also have idle timer, but the last workers are killed by trustee_thread())
next prev parent reply other threads:[~2013-07-26 3:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 10:52 [PATCH] workqueue: clear workers of a pool after the CPU is offline Lai Jiangshan
2013-07-25 15:31 ` Tejun Heo
2013-07-26 2:13 ` Lai Jiangshan
2013-07-26 3:07 ` Tejun Heo
2013-07-26 3:47 ` Lai Jiangshan [this message]
2013-07-26 10:22 ` Tejun Heo
2013-07-26 16:55 ` Lai Jiangshan
2013-07-26 17:03 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2013-02-20 17:04 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=51F1F138.2060902@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.