From: Darren Hart <dvhart@linux.intel.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
richard.purdie@linuxfoundation.org
Subject: Re: [PATCH 1/2] sched: allow SCHED_BATCH to preempt SCHED_IDLE tasks
Date: Tue, 22 Feb 2011 21:33:56 -0800 [thread overview]
Message-ID: <4D649C44.80107@linux.intel.com> (raw)
In-Reply-To: <1298434854.7856.24.camel@marge.simson.net>
On 02/22/2011 08:20 PM, Mike Galbraith wrote:
> On Tue, 2011-02-22 at 13:04 -0800, Darren Hart wrote:
>> Perform the test for SCHED_IDLE before testing for SCHED_BATCH (and ensure idle
>> tasks don't preempt idle tasks) so the non-interactive, but still important,
>> SCHED_BATCH tasks will run in favor of the very low priority SCHED_IDLE tasks.
>
> Yeah, that could be construed as a fairness fix for light SCHED_BATCH vs
> a heavy SCHED_IDLE. It should lower latencies for both when mixed.
>
> Acked-by: Mike Galbraith<efault@gmx.de>
>
> Nit below.
>
>> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
>> CC: Peter Zijlstra<peterz@infradead.org>
>> CC: Ingo Molnar<mingo@elte.hu>
>> CC: Richard Purdie<richard.purdie@linuxfoundation.org>
>> ---
>> kernel/sched_fair.c | 12 +++++++-----
>> 1 files changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
>> index 0c26e2d..ff04bbd 100644
>> --- a/kernel/sched_fair.c
>> +++ b/kernel/sched_fair.c
>> @@ -1857,16 +1857,18 @@ static void check_preempt_wakeup(struct rq *rq, struct task_struct *p, int wake_
>> if (test_tsk_need_resched(curr))
>> return;
>>
>> + /* Idle tasks are by definition preempted by non-idle tasks. */
>> + if (unlikely(curr->policy == SCHED_IDLE)&&
>> + likely(p->policy != SCHED_IDLE))
>> + goto preempt;
>> +
>
> if (unlikely(curr->policy == SCHED_IDLE&& p->policy != curr->policy))
> goto preempt;
>
> Looks better to me.
I have no opinion on the unlikely/likely optimizations. I chose the way
I did as I thought it was more consistent with the existing code. I'll
leave that to Peter and Ingo - let me know if I should resend.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-02-23 5:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:04 [PATCH 0/2] sched: SCHED_BATCH fixes Darren Hart
2011-02-22 21:04 ` [PATCH 1/2] sched: allow SCHED_BATCH to preempt SCHED_IDLE tasks Darren Hart
2011-02-23 4:20 ` Mike Galbraith
2011-02-23 5:31 ` Mike Galbraith
2011-02-23 5:33 ` Darren Hart [this message]
2011-03-04 11:49 ` [tip:sched/core] sched: Allow " tip-bot for Darren Hart
2011-02-22 21:04 ` [PATCH 2/2] sched: allow users with rtprio rlimit to change from SCHED_IDLE policy Darren Hart
2011-02-23 11:03 ` Peter Zijlstra
2011-02-23 11:13 ` Ingo Molnar
2011-02-23 11:17 ` Peter Zijlstra
2011-02-23 11:35 ` Ingo Molnar
2011-02-23 15:52 ` Darren Hart
2011-02-23 16:00 ` Peter Zijlstra
2011-02-23 16:07 ` Darren Hart
2011-02-23 21:28 ` Darren Hart
2011-02-24 11:49 ` Peter Zijlstra
2011-03-04 11:49 ` [tip:sched/core] sched: Allow users with sufficient RLIMIT_NICE " tip-bot for Darren Hart
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=4D649C44.80107@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=richard.purdie@linuxfoundation.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 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.