From: Felix Kuehling <felix.kuehling@amd.com>
To: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Dave Airlie <airlied@gmail.com>,
Philip Yang <Philip.Yang@amd.com>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Selecting CPUs for queuing work on
Date: Fri, 12 Aug 2022 16:26:47 -0400 [thread overview]
Message-ID: <82233e68-106f-39e9-b20d-7794eb7a8933@amd.com> (raw)
Hi workqueue maintainers,
In the KFD (amdgpu) driver we found a need to schedule bottom half
interrupt handlers on CPU cores different from the one where the
top-half interrupt handler runs to avoid the interrupt handler stalling
the bottom half in extreme scenarios. See my latest patch that tries to
use a different hyperthread on the same CPU core, or falls back to a
different core in the same NUMA node if that fails:
https://lore.kernel.org/all/20220811190433.1213179-1-Felix.Kuehling@amd.com/
Dave pointed out that the driver may not be the best place to implement
such logic and suggested that we should have an abstraction, maybe in
the workqueue code. Do you feel this is something that could or should
be provided by the core workqueue code? Or maybe some other place?
Thank you,
Felix
--
F e l i x K u e h l i n g
PMTS Software Development Engineer | Linux Compute Kernel
1 Commerce Valley Dr. East, Markham, ON L3T 7X6 Canada
(O) +1(289)695-1597
_ _ _ _____ _____
/ \ | \ / | | _ \ \ _ |
/ A \ | \M/ | | |D) ) /|_| |
/_/ \_\ |_| |_| |_____/ |__/ \| facebook.com/AMD | amd.com
next reply other threads:[~2022-08-12 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 20:26 Felix Kuehling [this message]
2022-08-12 20:30 ` Tejun Heo
2022-08-12 20:54 ` Felix Kuehling
2022-08-12 21:43 ` Tejun Heo
[not found] <20220824113315.2375-1-hdanton@sina.com>
2022-08-24 20:36 ` Felix Kuehling
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=82233e68-106f-39e9-b20d-7794eb7a8933@amd.com \
--to=felix.kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®