mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Libo Chen <libo.chen@oracle.com>
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
	linux-kernel@vger.kernel.org, David Vernet <void@manifault.com>,
	Andrea Righi <arighi@nvidia.com>,
	Changwoo Min <changwoo@igalia.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	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 14:14:51 -1000	[thread overview]
Message-ID: <Z9i6-_R_LLqt8mq4@slm.duckdns.org> (raw)
In-Reply-To: <e93710b9-4ae3-4d68-8e3f-65439e2cf9fd@oracle.com>

On Mon, Mar 17, 2025 at 05:12:25PM -0700, Libo Chen wrote:
> Just as Peter said, this is whole wake affinity thing is highly workload
> dependent. We have seen cases where even if there are idle cores in the
> prev node, it's still beneficial to cross the NUMA boundary. Will it make
> more sense to have the BPF scheduler implement/alter some of logic here so
> it can fit to different workload?

Oh yeah, multiple SCX schedulers already implement their own select_cpu().
This discussion is just around the default implementation which can be used
if a BPF scheduler doesn't want to implement its own.

Thanks.

-- 
tejun

  reply	other threads:[~2025-03-18  0:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17  8:28 Joel Fernandes
2025-03-17 17:08 ` Tejun Heo
2025-03-17 17:30   ` Andrea Righi
2025-03-17 17:44     ` Peter Zijlstra
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 [this message]
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=Z9i6-_R_LLqt8mq4@slm.duckdns.org \
    --to=tj@kernel.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=libo.chen@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®