From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, alex.shi@linaro.org
Subject: Re: [PATCH 4/4] sched: Idle task shortcut optimization
Date: Fri, 17 Jan 2014 16:26:13 +0100 [thread overview]
Message-ID: <52D94B95.2060704@linaro.org> (raw)
In-Reply-To: <20140117152310.GK11314@laptop.programming.kicks-ass.net>
On 01/17/2014 04:23 PM, Peter Zijlstra wrote:
> On Fri, Jan 17, 2014 at 04:06:45PM +0100, Daniel Lezcano wrote:
>>> I suppose we could write something like:
>>>
>>> struct task_struct *pick_next_task(struct rq *rq, struct task_struct *prev)
>>> {
>>> const struct sched_class *class;
>>> struct task_struct *p;
>>>
>>> again:
>>> if (likely(rq->nr_running)) {
>>>
>>> if (likely(rq->nr_running == rq->cfs.h_nr_running))
>>> return fair_sched_class.pick_next_task(rq, prev);
>>>
>>> for_each_class(class) {
>>> p = class->pick_next_task(rq, prev);
>>> if (p)
>>> return p;
>>> }
>>> }
>>>
>>> if (idle_balance(rq))
>>> goto again;
>>>
>>> rq->idle_stamp = rq_clock(rq);
>>>
>>> return idle_sched_class.pick_next_task(rq, prev);
>>> }
>>>
>>> Which keeps idle_balance() before put_prev_task(), and by using
>>> idle_sched_clas.pick_next_task() doesn't rape the idle class interface
>>> like you did :-)
>>
>> But put_prev_task is called before pick_next_task, so idle_balance() is
>> called after now, no ?
>
> No, put_prev_task() is called by the pick_next_task() that returns a
> task. So in the idle case above, the idle_sched_class.pick_next_task()
> will do the required put_prev_task().
Ah, ok. Let me try it.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2014-01-17 15:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 9:04 [PATCH 1/4] sched: Remove 'cpu' parameter for idle_balance() Daniel Lezcano
2014-01-17 9:04 ` [PATCH 2/4] sched: Fix race in idle_balance() Daniel Lezcano
2014-01-17 13:33 ` Peter Zijlstra
2014-01-17 13:44 ` Daniel Lezcano
2014-02-11 12:15 ` [tip:sched/core] " tip-bot for Daniel Lezcano
2014-01-17 9:04 ` [PATCH 3/4] sched: Move idle_stamp up to the core Daniel Lezcano
2014-02-11 12:16 ` [tip:sched/core] sched: Move rq->idle_stamp " tip-bot for Daniel Lezcano
2014-01-17 9:04 ` [PATCH 4/4] sched: Idle task shortcut optimization Daniel Lezcano
2014-01-17 14:09 ` Peter Zijlstra
2014-01-17 15:09 ` Daniel Lezcano
2014-01-17 15:23 ` Peter Zijlstra
2014-01-17 14:26 ` Peter Zijlstra
2014-01-17 15:06 ` Daniel Lezcano
2014-01-17 15:23 ` Peter Zijlstra
2014-01-17 15:26 ` Daniel Lezcano [this message]
2014-01-17 15:33 ` Peter Zijlstra
2014-01-17 16:06 ` Daniel Lezcano
2014-01-17 16:37 ` Daniel Lezcano
2014-01-17 16:45 ` [PATCH 1/2] sched/deadline: Fix compilation error Daniel Lezcano
2014-01-17 16:45 ` [PATCH 2/2] sched: Use idle task shortcut Daniel Lezcano
2014-01-21 8:41 ` [PATCH 4/4] sched: Idle task shortcut optimization Daniel Lezcano
2014-01-21 9:06 ` Peter Zijlstra
2014-01-21 9:28 ` Daniel Lezcano
2014-02-11 12:15 ` [tip:sched/core] sched: Remove 'cpu' parameter from idle_balance( ) tip-bot for Daniel Lezcano
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=52D94B95.2060704@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alex.shi@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome