From: Peter Zijlstra <peterz@infradead.org>
To: Andrea Righi <andrea.righi@linux.dev>
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Always call put_prev_task() with scx enabled
Date: Mon, 14 Oct 2024 10:36:08 +0200 [thread overview]
Message-ID: <20241014083608.GU17263@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241013173928.20738-1-andrea.righi@linux.dev>
On Sun, Oct 13, 2024 at 07:39:28PM +0200, Andrea Righi wrote:
> With the consolidation of put_prev_task/set_next_task(), we are now
> skipping the sched_ext ops.stopping/running() transitions when the
> previous and next tasks are the same, see commit 436f3eed5c69 ("sched:
> Combine the last put_prev_task() and the first set_next_task()").
>
> While this optimization makes sense in general, it can negatively impact
> performance in some user-space schedulers, that expect to handle such
> transitions when tasks exhaust their timeslice (see SCX_OPS_ENQ_LAST).
>
> For example, scx_rustland suffers a significant performance regression
> (e.g., gaming benchmarks drop from ~60fps to ~10fps).
>
> To fix this, ensure that put_prev_task()/set_next_task() are never
> skipped when the scx scheduling class is enabled, allowing the scx class
> to handle such transitions.
>
> This change restores the previous behavior, fixing the performance
> regression in scx_rustland.
>
> Link: https://github.com/sched-ext/scx/issues/788
How persistent are links like that? In general I strongly discourage
links to things not pointing to kernel.org resources.
> @@ -2523,6 +2508,21 @@ DECLARE_STATIC_KEY_FALSE(__scx_switched_all); /* all fair class tasks on SCX */
> #define scx_switched_all() false
> #endif /* !CONFIG_SCHED_CLASS_EXT */
>
> +static inline void put_prev_set_next_task(struct rq *rq,
> + struct task_struct *prev,
> + struct task_struct *next)
> +{
> + WARN_ON_ONCE(rq->curr != prev);
> +
> + __put_prev_set_next_dl_server(rq, prev, next);
> +
> + if (next == prev && !scx_enabled())
> + return;
Does that not also want to include a 'next->sched_class ==
&ext_sched_class' clause ? And a comment?
> +
> + prev->sched_class->put_prev_task(rq, prev, next);
> + next->sched_class->set_next_task(rq, next, true);
> +}
And is there really no way scx can infer this happened? We just did pick
after all, that can see this coming a mile of.
next prev parent reply other threads:[~2024-10-14 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 17:39 [PATCH] sched_ext: Always call put_prev_task() with scx enabled Andrea Righi
2024-10-14 8:36 ` Peter Zijlstra [this message]
2024-10-14 15:00 ` Andrea Righi
2024-10-14 15:43 ` Andrea Righi
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=20241014083608.GU17263@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrea.righi@linux.dev \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.