From: "Chuck Lever" <cel@kernel.org>
To: "Tejun Heo" <tj@kernel.org>
Cc: "Trond Myklebust" <trondmy@kernel.org>,
"Anna Schumaker" <anna@kernel.org>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
linux-nfs@vger.kernel.org,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2 5/8] workqueue: add workqueue_set_affn_scope()
Date: Thu, 03 Sep 2026 09:41:38 -0400 [thread overview]
Message-ID: <d9bde347-6ca2-48e7-b0d2-768bfb7c653a@app.fastmail.com> (raw)
In-Reply-To: <aph6yYag8LeZxmyn@slm.duckdns.org>
On Wed, Sep 2, 2026, at 3:36 PM, Tejun Heo wrote:
> On Wed, Sep 02, 2026 at 03:28:50PM -0400, Chuck Lever wrote:
>> An unbound workqueue's affinity scope can be changed only through
>> sysfs. A module whose workqueue contends on the pool lock at the
>> default scope has no in-kernel way to select a finer one, because
>> alloc_workqueue_attrs() and apply_workqueue_attrs() are not
>> exported. Exporting them would also invite a caller to apply freshly
>
> BTW, please feel free to export them.
>
>> +int workqueue_set_affn_scope(struct workqueue_struct *wq,
>> + enum wq_affn_scope affn_scope)
>
> No need for the line break.
>
>> +{
>> + struct workqueue_attrs *attrs;
>> + int ret = -ENOMEM;
>> +
>> + if ((unsigned int)affn_scope >= WQ_AFFN_NR_TYPES)
>> + return -EINVAL;
>> +
>> + mutex_lock(&wq_pool_mutex);
>> + attrs = alloc_workqueue_attrs();
>
> Maybe alloc outside mutex and use alloc and mutex guards?
>
> Thanks.
>
> --
> tejun
All applied to v3 (still unposted). Sorry all this has taken so long.
--
Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
next prev parent reply other threads:[~2026-09-03 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:28 [PATCH RFC v2 0/8] Reduce lock contention in the NFS client Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 1/8] SUNRPC: Use atomic_t for XID allocation Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 2/8] SUNRPC: Split recv_lock out of xprt->queue_lock Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 3/8] SUNRPC: Set WQ_SYSFS on rpciod and xprtiod Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 4/8] NFS: Set WQ_SYSFS on nfsiod Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 5/8] workqueue: add workqueue_set_affn_scope() Chuck Lever
2026-09-02 19:36 ` Tejun Heo
2026-09-03 13:41 ` Chuck Lever [this message]
2026-09-02 19:28 ` [PATCH RFC v2 6/8] SUNRPC: Reduce rpciod workqueue contention Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 7/8] NFS: Reduce nfsiod " Chuck Lever
2026-09-02 19:28 ` [PATCH RFC v2 8/8] SUNRPC: Reduce xprtiod " Chuck Lever
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=d9bde347-6ca2-48e7-b0d2-768bfb7c653a@app.fastmail.com \
--to=cel@kernel.org \
--cc=anna@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tj@kernel.org \
--cc=trondmy@kernel.org \
/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®