[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZJNsZUxXFUuG34Dw@slm.duckdns.org>
Date: Wed, 21 Jun 2023 11:32:21 -1000
From: Tejun Heo <tj@...nel.org>
To: Yuanhan Zhang <zyhtheonly@...il.com>
Cc: jiangshanlai@...il.com, linux-kernel@...r.kernel.org,
pmladek@...e.com, zyhtheonly@...h.net, zwp10758@...il.com,
tiozhang@...iglobal.com, fuyuanli@...iglobal.com
Subject: Re: [PATCH] workqueue: introduce queue_work_cpumask to queue work
onto a given cpumask
Hello,
On Tue, Jun 13, 2023 at 06:25:44PM +0800, Yuanhan Zhang wrote:
> If I have several kinds of works, and I'd like to make them run on
> different cpusets
> (so it is not ideal to put them on WQ_UNBOUND).
So, you can achieve that by creating a workqueue for each group of work
items. Each workqueue is just a front-end to shared pools of workers and
groups work items according to their attributes and flush grouping needs,
which is what you're asking for here.
Thanks.
--
tejun
Powered by blists - more mailing lists