mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Mitchell Erblich" <erblichs@earthlink.net>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Question: RT schedular : task_tick_rt(struct rq *rq, struct task_struct *p) : decreases overhead when rq->nr_running == 1
Date: Thu, 9 Aug 2007 10:39:13 +0200	[thread overview]
Message-ID: <b647ffbd0708090139k2ddcc100q443821a03c6733f3@mail.gmail.com> (raw)
In-Reply-To: <20070809083606.GA24130@elte.hu>

On 09/08/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> FYI, that's the patch i applied:

Thanks. Added my SOB below.

>
> --------------------------->
> Subject: sched: optimize task_tick_rt() a bit
> From: Dmitry Adamushko <dmitry.adamushko@gmail.com>
>
> Mitchell Erblich suggested a change to not requeue SCHED_RR
> tasks if there's only a single task on the runqueue, by
> checking for rq->nr_running == 1.
>
> provide a more efficient implementation of that, to check that
> particular RT priority-queue only.
>
> [ From: mingo@elte.hu ]
>
> Also first requeue the task then set need_resched - results
> in slightly better machine-instruction ordering. Also clean
> up the code a bit.
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>


Signed-off-by: Dmitry Adamushko <dmitry.adamushko@gmail.com>


> ---
>  kernel/sched_rt.c |   11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
>
> Index: linux/kernel/sched_rt.c
> ===================================================================
> --- linux.orig/kernel/sched_rt.c
> +++ linux/kernel/sched_rt.c
> @@ -207,10 +207,15 @@ static void task_tick_rt(struct rq *rq,
>                 return;
>
>         p->time_slice = static_prio_timeslice(p->static_prio);
> -       set_tsk_need_resched(p);
>
> -       /* put it at the end of the queue: */
> -       requeue_task_rt(rq, p);
> +       /*
> +        * Requeue to the end of queue if we are not the only element
> +        * on the queue:
> +        */
> +       if (p->run_list.prev != p->run_list.next) {
> +               requeue_task_rt(rq, p);
> +               set_tsk_need_resched(p);
> +       }
>  }
>
>  static struct sched_class rt_sched_class __read_mostly = {
>


-- 
Best regards,
Dmitry Adamushko

      reply	other threads:[~2007-08-09  8:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 22:54 Mitchell Erblich
2007-08-08 12:34 ` Ingo Molnar
2007-08-09  8:11   ` Dmitry Adamushko
2007-08-09  8:26     ` Ingo Molnar
2007-08-09  8:36       ` Ingo Molnar
2007-08-09  8:39         ` Dmitry Adamushko [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=b647ffbd0708090139k2ddcc100q443821a03c6733f3@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=erblichs@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®