From: "Christian König" <christian.koenig@amd.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, 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>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH 1/4] drm/amdgpu: replace use of system_unbound_wq with system_dfl_wq
Date: Fri, 31 Oct 2025 09:44:28 +0100 [thread overview]
Message-ID: <841680ea-1086-4380-910e-8a836b711a42@amd.com> (raw)
In-Reply-To: <CAAofZF7d+t8Qqojawes8WAR2YOWz7vMtgt2y=ofJHN6mChX6DQ@mail.gmail.com>
On 10/31/25 09:42, Marco Crivellari wrote:
> On Thu, Oct 30, 2025 at 6:14 PM Christian König
> <christian.koenig@amd.com> wrote:
>> [...]
>> In all the cases below we actually want the work to run on a different CPU than the current one.
>>
>> So using system_unbound_wq seems to be more appropriate.
>
> Hello Christian,
>
> system_dfl_wq is the new workqueue that will replace
> system_unbound_wq, but the behavior is the same.
> So, if you need system_unbound_wq, it means system_dfl_wq is fine here.
Ah, ok thanks! In that case I'm fine with the change.
It sounded like system_dfl_wq is the new per CPU wq.
Regards,
Christian.
>
> Thanks!
next prev parent reply other threads:[~2025-10-31 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 16:10 [PATCH 0/4] replace old wq(s), added WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-10-30 16:10 ` [PATCH 1/4] drm/amdgpu: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-10-30 17:14 ` Christian König
2025-10-31 8:42 ` Marco Crivellari
2025-10-31 8:44 ` Christian König [this message]
2025-10-30 16:10 ` [PATCH 2/4] drm/amdgpu: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-10-30 17:10 ` Christian König
2025-10-31 9:01 ` Marco Crivellari
2025-11-03 15:07 ` Christian König
2025-10-30 16:10 ` [PATCH 3/4] amd/amdkfd: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-10-30 17:15 ` Christian König
2025-10-31 8:48 ` Marco Crivellari
2025-10-31 13:12 ` Philip Yang
2025-11-03 15:01 ` Marco Crivellari
2025-10-30 16:10 ` [PATCH 4/4] drm/radeon: " Marco Crivellari
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=841680ea-1086-4380-910e-8a836b711a42@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=simona@ffwll.ch \
--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