mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dario Faggioli <raistlin@linux.it>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Gregory Haskins <ghaskins@novell.com>,
	Mike Galbraith <efault@gmx.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] sched: leave sched_setscheduler earlier if possible.
Date: Thu, 24 Mar 2011 10:21:59 -0400	[thread overview]
Message-ID: <1300976519.14261.141.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1300971618.3960.82.camel@Palantir>

On Thu, 2011-03-24 at 14:00 +0100, Dario Faggioli wrote:
> sched_setscheduler (in sched.c) is called in order of changing the
> scheduling policy and/or the real-time priority of a task. Thus,
> if we find out that neither of those are actually being modified, it
> is possible to return earlier and save the overhead of a full
> deactivate+activate cycle of the task in question.
> 
> Beside that, if we have more than one SCHED_FIFO task with the same
> priority on the same rq (which means they share the same priority queue)
> having one of them changing its position in the priority queue because of
> a sched_setscheduler (as it happens by means of the deactivate+activate)
> that does not actually change the priority violates POSIX which states,
> for SCHED_FIFO:
> 
> "If a thread whose policy or priority has been modified by
> pthread_setschedprio() is a running thread or is runnable, the effect on
> its position in the thread list depends on the direction of the
> modification, as follows: a. <...> b. If the priority is unchanged, the
> thread does not change position in the thread list. c. <...>"
> 
> (http://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_08.html)
> 
> Signed-off-by: Dario Faggioli <raistlin@linux.it>

Acked-by: Steven Rostedt <rostedt@goodmis.org>

> ---
>  kernel/sched.c |   10 ++++++++++
>  1 files changed, 10 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/sched.c b/kernel/sched.c
> index c5ae6bc..d73bbc5 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c


> @@ -4998,6 +4998,16 @@ recheck:

Peter, this is why I prefer:

 recheck:
over
recheck:

-- Steve


>  		return -EINVAL;
>  	}
>  
> +	/*
> +	 * If not changing anything there's no need to proceed further
> +	 */
> +	if (unlikely(policy == p->policy && (!rt_policy(policy) ||
> +	    param->sched_priority == p->rt_priority))) {
> +			__task_rq_unlock(rq);
> +			raw_spin_unlock_irqrestore(&p->pi_lock, flags);
> +			return 0;
> +	}
> +
>  #ifdef CONFIG_RT_GROUP_SCHED
>  	if (user) {
>  		/*
> -- 
> 1.7.4.1
> 



  reply	other threads:[~2011-03-24 14:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 13:00 Dario Faggioli
2011-03-24 14:21 ` Steven Rostedt [this message]
2011-03-25 10:28   ` Peter Zijlstra
2011-03-25 12:52     ` Steven Rostedt
2011-03-25 13:07       ` Peter Zijlstra
2011-03-25 22:36         ` Junio C Hamano
2011-03-26 10:26           ` Peter Zijlstra
2011-03-26 10:30             ` Peter Zijlstra
2011-03-31 12:39 ` [tip:sched/urgent] sched: Leave sched_setscheduler() earlier if possible, do not disturb SCHED_FIFO tasks tip-bot for Dario Faggioli

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=1300976519.14261.141.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=efault@gmx.de \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=raistlin@linux.it \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®