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 2/4] drm/amdgpu: replace use of system_wq with system_percpu_wq
Date: Mon, 3 Nov 2025 16:07:20 +0100 [thread overview]
Message-ID: <0ea75705-2824-44ab-8583-4a06fbf61b10@amd.com> (raw)
In-Reply-To: <CAAofZF5pSB-kJVr_PJbo_845VbpaB1Fbf+yeA74sWOU_vXfypQ@mail.gmail.com>
On 10/31/25 10:01, Marco Crivellari wrote:
> On Thu, Oct 30, 2025 at 6:10 PM Christian König
> <christian.koenig@amd.com> wrote:
>> [...]
>> In this particular use case we actually don't want the percpu wq.
>>
>> This can execute on any CPU except for the current one.
>>
>> Regards,
>> Christian.
>>
>>> exit:
>>> if (amdgpu_sriov_vf(adev)) {
>>
>
> Hi Christian,
>
> like for the unbound workqueue also the system_percpu_wq is just a
> rename for system_wq.
> Technically I changed the workqueue because we added in the code two wq:
> - system_percpu_wq
> - system_dfl_wq
>
> You can see the commits mentioned in the cover letter, shared also below:
>
> - commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> - commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
>
> So basically the behavior is the same.
>
> But if it would be beneficial to have an unbound wq, I can send the v2
> with the change!
Please do so. The purpose of offloading that into a work item is to execute it on a different CPU.
I wasn't aware that the system_wq was CPU bound at all.
Thanks to taking care of that,
Christian.
> We did so also for other subsystems.
>
> Thanks!
>
>
>
> --
>
> Marco Crivellari
>
> L3 Support Engineer, Technology & Product
next prev parent reply other threads:[~2025-11-03 15:07 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
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 [this message]
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=0ea75705-2824-44ab-8583-4a06fbf61b10@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
all inboxes | Powered by JetHome®