[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAofZF7d+t8Qqojawes8WAR2YOWz7vMtgt2y=ofJHN6mChX6DQ@mail.gmail.com>
Date: Fri, 31 Oct 2025 09:42:48 +0100
From: Marco Crivellari <marco.crivellari@...e.com>
To: Christian König <christian.koenig@....com>
Cc: linux-kernel@...r.kernel.org, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, Tejun Heo <tj@...nel.org>,
Lai Jiangshan <jiangshanlai@...il.com>, Frederic Weisbecker <frederic@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>, Michal Hocko <mhocko@...e.com>,
Alex Deucher <alexander.deucher@....com>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>
Subject: Re: [PATCH 1/4] drm/amdgpu: replace use of system_unbound_wq with system_dfl_wq
On Thu, Oct 30, 2025 at 6:14 PM Christian König
<christian.koenig@....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.
Thanks!
--
Marco Crivellari
L3 Support Engineer, Technology & Product
Powered by blists - more mailing lists