From: Michael wang <wangyun@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched: Push down pre_schedule() and idle_balance ()
Date: Fri, 14 Feb 2014 10:13:48 +0800 [thread overview]
Message-ID: <52FD7BDC.7020509@linux.vnet.ibm.com> (raw)
In-Reply-To: <52FC3D5B.7000808@linux.vnet.ibm.com>
On 02/13/2014 11:34 AM, Michael wang wrote:
> On 02/12/2014 06:22 PM, Peter Zijlstra wrote:
> [snip]
>>
>> Yes I think there might be a problem here because of how we re-arranged
>> things. Let me brew of pot of tea and try to actually wake up.
>>
>> I suspect we might be good if we clear the need_resched flags before
>> calling pick_next_task. Then any RT/DL task that gets moved here will
>> set need resched, and we'll retry the pick_next_task loop.
>
> That sounds better, some thing like this?
Hmm... need a little adjustments, will post formal patch with some test
later.
Regards,
Michael Wang
>
>
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index fb9764f..56a2e1f 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2688,8 +2688,8 @@ need_resched:
> if (prev->on_rq || rq->skip_clock_update < 0)
> update_rq_clock(rq);
>
> - next = pick_next_task(rq, prev);
> clear_tsk_need_resched(prev);
> + next = pick_next_task(rq, prev);
> clear_preempt_need_resched();
> rq->skip_clock_update = 0;
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 235cfa7..48a9500 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4784,7 +4784,18 @@ idle:
> rq->idle_stamp = rq_clock(rq);
> if (idle_balance(rq)) { /* drops rq->lock */
> rq->idle_stamp = 0;
> - goto again;
> + /*
> + * Before we start to pick one of the pulled fair entities, take
> + * care if some RT/DL tasks has been enqueued during the time
> + * we release rq-lock inside idle_balance().
> + *
> + * In such cases, since clear_tsk_need_resched() was done
> + * already, need_resched() will imply the request to sched-in
> + * the enqueued RT/DL tasks, so don't 'goto again' to make sure
> + * the priority.
> + */
> + if (rq->nr_running == rq->cfs.h_nr_running || !need_resched())
> + goto again;
>
>
>
> I like tea BTW, drink every day :)
>
> Regards,
> Michael Wang
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
prev parent reply other threads:[~2014-02-14 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 12:17 [tip:sched/core] sched: Push down pre_schedule() and idle_balance () tip-bot for Peter Zijlstra
2014-02-12 6:26 ` Michael wang
2014-02-12 10:22 ` Peter Zijlstra
2014-02-13 3:34 ` Michael wang
2014-02-14 2:13 ` Michael wang [this message]
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=52FD7BDC.7020509@linux.vnet.ibm.com \
--to=wangyun@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).