From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sched: Optimize pick_next_task for idle_sched_class too
Date: Thu, 19 Jan 2017 18:44:08 +0100 [thread overview]
Message-ID: <20170119174408.GN6485@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170119101703.2abeaeb6@gandalf.local.home>
On Thu, Jan 19, 2017 at 10:17:03AM -0500, Steven Rostedt wrote:
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 154fd68..e2c6d3b 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3259,13 +3259,15 @@ static inline struct task_struct *
> pick_next_task(struct rq *rq, struct task_struct *prev, struct pin_cookie cookie)
> {
> const struct sched_class *class = &fair_sched_class;
> + const struct sched_class *idle_class = &idle_sched_class;
> struct task_struct *p;
>
> /*
> * Optimization: we know that if all tasks are in
> * the fair class we can call that function directly:
> */
> - if (likely(prev->sched_class == class &&
> + if (likely((prev->sched_class == class ||
> + prev->sched_class == idle_class) &&
> rq->nr_running == rq->cfs.h_nr_running)) {
OK, so I hate this patch because it makes the condition more complex,
and while staring at what it does for code generation I couldn't for the
life of me figure out why we care about prev->sched_class to begin with.
(we used to, but the current code not so much)
So I simply removed that entire clause, like below, and lo and behold,
the system booted...
Could you give it a spin to see if anything comes apart?
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 49ce1cb..51ca21e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3321,15 +3321,14 @@ static inline void schedule_debug(struct task_struct *prev)
static inline struct task_struct *
pick_next_task(struct rq *rq, struct task_struct *prev, struct rq_flags *rf)
{
- const struct sched_class *class = &fair_sched_class;
+ const struct sched_class *class;
struct task_struct *p;
/*
* Optimization: we know that if all tasks are in
* the fair class we can call that function directly:
*/
- if (likely(prev->sched_class == class &&
- rq->nr_running == rq->cfs.h_nr_running)) {
+ if (likely(rq->nr_running == rq->cfs.h_nr_running)) {
p = fair_sched_class.pick_next_task(rq, prev, rf);
if (unlikely(p == RETRY_TASK))
goto again;
next prev parent reply other threads:[~2017-01-19 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 15:17 [PATCH] sched: Optimize pick_next_task for idle_sched_class too Steven Rostedt
2017-01-19 17:44 ` Peter Zijlstra [this message]
2017-01-20 16:14 ` Steven Rostedt
2017-01-20 16:16 ` Steven Rostedt
2017-01-20 16:52 ` Peter Zijlstra
2017-01-30 11:54 ` [tip:sched/core] sched/core: Optimize pick_next_task() for idle_sched_class tip-bot for Peter Zijlstra
2017-02-23 10:34 ` [PATCH] sched: Optimize pick_next_task for idle_sched_class too Pavan Kondeti
2017-02-23 13:54 ` Peter Zijlstra
2017-02-23 15:15 ` Pavan Kondeti
2017-02-23 15:25 ` Peter Zijlstra
2017-02-23 16:37 ` Peter Zijlstra
2017-02-23 17:29 ` Pavan Kondeti
2017-02-23 17:45 ` Peter Zijlstra
2017-02-23 17:54 ` Peter Zijlstra
2017-02-27 17:54 ` Steven Rostedt
2017-03-01 15:53 ` Steven Rostedt
2017-03-01 16:03 ` Peter Zijlstra
2017-03-01 16:19 ` Steven Rostedt
2017-03-01 16:22 ` Peter Zijlstra
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=20170119174408.GN6485@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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