linux-kernel - Re: [PATCH 4/5] workqueue: Automatically mark CPU-hogging work items CPU

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>] [day] [month] [year] [list]

Message-ID: <ZEAMkyXxq_vbQpxe@slm.duckdns.org>
Date:   Wed, 19 Apr 2023 05:45:23 -1000
From:   Tejun Heo <tj@...nel.org>
To:     Hillf Danton <hdanton@...a.com>
Cc:     jiangshanlai@...il.com, torvalds@...ux-foundation.org,
        peterz@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/5] workqueue: Automatically mark CPU-hogging work items
 CPU_INTENSIVE

Hello,

On Wed, Apr 19, 2023 at 09:45:52AM +0800, Hillf Danton wrote:
...
> Need to wake up another worker in case the current one with
> WORKER_CPU_INTENSIVE set is going to sleep with works left behind.

Please see below.

> > +
> > +		pool->nr_running--;
> >  	}
> >  
> > -	pool->nr_running--;
> >  	if (need_more_worker(pool))
> >  		wake_up_worker(pool);

That's what this block is for.

Thanks.

-- 
tejun