mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
	pmladek@suse.com, zyhtheonly@gmail.com, zyhtheonly@yeah.net,
	zwp10758@gmail.com
Subject: Re: [PATCH] workqueue: introduce queue_work_cpumask to queue work onto a given cpumask
Date: Thu, 8 Jun 2023 12:52:44 -1000	[thread overview]
Message-ID: <ZIJbvCcaqjzNteWs@slm.duckdns.org> (raw)
In-Reply-To: <20230606093135.GA9077@didi-ThinkCentre-M930t-N000>

On Tue, Jun 06, 2023 at 05:31:35PM +0800, Tio Zhang wrote:
> Introduce queue_work_cpumask to queue work on a "random" CPU onto a given
> cpumask. It would be helpful when devices/modules want to assign works on
> different cpusets but do not want to maintain extra workqueues, since they
> have to alloc different workqueues and set different
> workqueue_attrs->cpumask in the past times.
> 
> For now only available for unbound workqueues, We will try to further
> patch it.
> And default to the first CPU that is in the intersection of the cpumask
> given and the online cpumask.
> The only exception is if the CPU is local in the cpuset we will just use
> the current CPU.
> 
> The implementation and comments are referenced from
> 'commit 8204e0c1113d ("workqueue: Provide queue_work_node to queue work
> near a given NUMA node")'

Can you elaborate the intended use cases?

Thanks.

-- 
tejun

  parent reply	other threads:[~2023-06-08 22:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  9:31 Tio Zhang
2023-06-08  6:33 ` Lai Jiangshan
2023-06-08 22:52 ` Tejun Heo [this message]
     [not found]   ` <CAEQmJ=gLCzoxUR9Eas+w9=bV7Tg5SZNb+TufanNXnPxR8cn5iQ@mail.gmail.com>
2023-06-09  6:23     ` Yuanhan Zhang
2023-06-09  6:28   ` Yuanhan Zhang
2023-06-12 17:54     ` Tejun Heo
2023-06-13 10:25       ` Yuanhan Zhang
2023-06-21 21:32         ` Tejun Heo

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=ZIJbvCcaqjzNteWs@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=zwp10758@gmail.com \
    --cc=zyhtheonly@gmail.com \
    --cc=zyhtheonly@yeah.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®