[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YRv2XP5F+lv41FE3@slm.duckdns.org>
Date: Tue, 17 Aug 2021 07:48:12 -1000
From: Tejun Heo <tj@...nel.org>
To: Lai Jiangshan <jiangshanlai@...il.com>
Cc: linux-kernel@...r.kernel.org, lizefan.x@...edance.com,
lizhe.67@...edance.com, Lai Jiangshan <laijs@...ux.alibaba.com>
Subject: Re: [PATCH 0/6] workqueue: Make flush_workqueue() also watch
flush_work()
On Tue, Aug 17, 2021 at 09:32:33AM +0800, Lai Jiangshan wrote:
> Due to historical convenience, we used WORK_NO_COLOR for barrier work items
> queued by flush_work(). The color has two purposes:
> Not participate in flushing
> Not participate in nr_active
>
> Only the second purpose is obligatory. So the plan is to mark barrier
> work items inactive without using WORK_NO_COLOR in patch4 so that we can
> assign a flushing color to them in patch5.
This is great work. Applied to wq/for-5.15.
Thanks.
--
tejun
Powered by blists - more mailing lists