linux-kernel - Re: [PATCH] workqueue: clear workers of a pool after the CPU is offline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130726030711.GA30195@mtj.dyndns.org>
Date:	Thu, 25 Jul 2013 23:07:11 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] workqueue: clear workers of a pool after the CPU is
 offline

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?

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/