From: Peter Zijlstra <peterz@infradead.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: Tejun Heo <tj@kernel.org>, Joel Fernandes <joelagnelf@nvidia.com>,
linux-kernel@vger.kernel.org, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH RFC] sched_ext: Choose prev_cpu if idle and cache affine without WF_SYNC
Date: Mon, 17 Mar 2025 18:44:31 +0100 [thread overview]
Message-ID: <20250317174431.GI6888@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <Z9hcUSp6P72wT5ig@gpd3>
On Mon, Mar 17, 2025 at 06:30:57PM +0100, Andrea Righi wrote:
> I guess the question is: what is more expensive in general on task wakeup?
> 1) a cross-node migration or 2) running on a partially busy SMT core?
That totally depends on both the workload and the actual machine :/
If you have 'fast' numa and not a very big footprint, the numa
migrations aren't too bad. OTOH if you have sucky numa or your memory
footprint is significant, then running on the wrong node is super
painful.
next prev parent reply other threads:[~2025-03-17 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 8:28 [PATCH RFC] sched_ext: Choose prev_cpu if idle and cache affine without WF_SYNC Joel Fernandes
2025-03-17 17:08 ` Tejun Heo
2025-03-17 17:30 ` Andrea Righi
2025-03-17 17:44 ` Peter Zijlstra [this message]
2025-03-18 5:17 ` Andrea Righi
2025-03-17 22:11 ` Joel Fernandes
2025-03-18 5:09 ` Andrea Righi
2025-03-18 17:00 ` Joel Fernandes
2025-03-18 17:46 ` Andrea Righi
2025-03-18 22:37 ` Joel Fernandes
2025-03-17 22:07 ` Joel Fernandes
2025-03-17 22:25 ` Tejun Heo
2025-03-17 22:45 ` Joel Fernandes
2025-03-18 0:12 ` Libo Chen
2025-03-18 0:14 ` Tejun Heo
2025-03-17 17:20 ` Andrea Righi
2025-03-17 22:44 ` Joel Fernandes
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=20250317174431.GI6888@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=joelagnelf@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.com \
/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