From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
kernel@collabora.com, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Shreeya Patel <shreeya.patel@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] media: synopsys: hdmirx: replace use of system_unbound_wq with system_dfl_wq
Date: Wed, 11 Feb 2026 19:45:07 +0300 [thread overview]
Message-ID: <bc8904f1-bc24-4558-861f-5230e0b73181@collabora.com> (raw)
In-Reply-To: <CAAofZF7uLAd-tDnQq9joZm5vZunVr64QfF+ZFH-OoYfqG2OrCg@mail.gmail.com>
On 2/10/26 17:36, Marco Crivellari wrote:
> On Mon, Feb 9, 2026 at 10:18 PM Dmitry Osipenko
> <dmitry.osipenko@collabora.com> wrote:
>> Alright, looking further at the code, apparently there is nothing
>> special RE the two unbound work queues. See some parts of kernel already
>> moved to system_dfl. Would be great is this all was clarified in the
>> commit message.
>>
>> Acked-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>
> Hi,
>
> If you want I can send a new version with the improved commit log:
>
> ---
>
> This patch continues the effort to refactor workqueue APIs, which has begun
> with the changes introducing new workqueues and a new alloc_workqueue flag:
>
> commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
>
> The point of the refactoring is to eventually alter the default behavior of
> workqueues to become unbound by default so that their workload placement is
> optimized by the scheduler.
>
> Before that to happen, workqueue users must be converted to the better named
> new workqueues with no intended behaviour changes:
>
> system_wq -> system_percpu_wq
> system_unbound_wq -> system_dfl_wq
>
> This way the old obsolete workqueues (system_wq, system_unbound_wq) can be
> removed in the future.
>
> Link: https://lore.kernel.org/all/20250221112003.1dSuoGyc@linutronix.de/
>
> ---
>
> Let me know what's best.
That's better, feel free to send the v2. Thanks!
--
Best regards,
Dmitry
prev parent reply other threads:[~2026-02-11 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 10:20 Marco Crivellari
2025-11-04 12:45 ` Dmitry Osipenko
2025-11-04 16:44 ` Marco Crivellari
2026-02-04 11:49 ` Marco Crivellari
2026-02-09 20:46 ` Dmitry Osipenko
2026-02-09 21:18 ` Dmitry Osipenko
2026-02-10 14:36 ` Marco Crivellari
2026-02-11 16:45 ` Dmitry Osipenko [this message]
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=bc8904f1-bc24-4558-861f-5230e0b73181@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mchehab@kernel.org \
--cc=mhocko@suse.com \
--cc=shreeya.patel@collabora.com \
--cc=tj@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®