From: Tejun Heo <tj@kernel.org>
To: Ryo Takakura <ryotkkr98@gmail.com>
Cc: song@kernel.org, yukuai3@huawei.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md/raid5: unset WQ_CPU_INTENSIVE for raid5 unbound workqueue
Date: Mon, 2 Jun 2025 07:23:22 -1000 [thread overview]
Message-ID: <aD3eCqdH5nwftMiu@slm.duckdns.org> (raw)
In-Reply-To: <20250601013702.64640-1-ryotkkr98@gmail.com>
On Sun, Jun 01, 2025 at 10:37:02AM +0900, Ryo Takakura wrote:
> When specified with WQ_CPU_INTENSIVE, the workqueue doesn't
> participate in concurrency management. This behaviour is already
> accounted for WQ_UNBOUND workqueues given that they are assigned
> to their own worker threads.
>
> Unset WQ_CPU_INTENSIVE as the use of flag has no effect when
> used with WQ_UNBOUND.
>
> Signed-off-by: Ryo Takakura <ryotkkr98@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2025-06-02 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 1:37 [PATCH] md/raid5: unset WQ_CPU_INTENSIVE for raid5 unbound workqueue Ryo Takakura
2025-06-02 17:23 ` Tejun Heo [this message]
2025-06-14 6:42 ` Yu Kuai
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=aD3eCqdH5nwftMiu@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=ryotkkr98@gmail.com \
--cc=song@kernel.org \
--cc=yukuai3@huawei.com \
/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