The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Sébastien Dugué" <sebastien.dugue@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux RT Users <linux-rt-users@vger.kernel.org>,
	Darren Hart <dvhltc@us.ibm.com>,
	john stultz <johnstul@us.ibm.com>,
	Jean Pierre Dion <jean-pierre.dion@bull.net>,
	Gilles Carry <Gilles.Carry@ext.bull.net>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Patch RT] Fix CFS load balancing for RT tasks
Date: Wed, 11 Jul 2007 19:06:20 +0200	[thread overview]
Message-ID: <1184173580.12353.105.camel@chaos> (raw)
In-Reply-To: <20070711164708.48907792@frecb000686.frec.bull.fr>

On Wed, 2007-07-11 at 16:47 +0200, Sébastien Dugué wrote:
>   The following patch fixes this by re-enabling the RT overload detection
> for the CFS. It may not be the right solution, maybe it should be incorporated
> into the other load balancing mechanisms. I did not digg deep enough yet
> to make that call ;-)
> 
>   P.S. Thanks to Steven Rostedt for logdev which is proving invaluable in
>        cases like this.
> 
>   Sébastien.

Nice catch. That was dropped during the CFS -> -rt merge.

	tglx

> ------------------
> 
>   The RT overload mechanism of the O(1) scheduler has not been activated
> in the new CFS.
> 
>   This patch fixes that by inserting calls to inc_rt_tasks() and dec_rt_tasks()
> in enqueue_task_rt() and dequeue_task_rt() respectively, which enables the
> balance_rt_tasks() to be run in the rt_overload case.
> 
> 
> Signed-off-by: Sébastien Dugué <sebastien.dugue@bull.net>
> 
> ---
>  kernel/sched_rt.c |    4 ++++
>  1 file changed, 4 insertions(+)
> 
> Index: linux-2.6.21.5-rt20/kernel/sched_rt.c
> ===================================================================
> --- linux-2.6.21.5-rt20.orig/kernel/sched_rt.c	2007-07-11 10:46:26.000000000 +0200
> +++ linux-2.6.21.5-rt20/kernel/sched_rt.c	2007-07-11 10:46:50.000000000 +0200
> @@ -32,6 +32,8 @@ enqueue_task_rt(struct rq *rq, struct ta
>  
>  	list_add_tail(&p->run_list, array->queue + p->prio);
>  	__set_bit(p->prio, array->bitmap);
> +
> +	inc_rt_tasks(p, rq);
>  }
>  
>  /*
> @@ -44,6 +46,8 @@ dequeue_task_rt(struct rq *rq, struct ta
>  
>  	update_curr_rt(rq, now);
>  
> +	dec_rt_tasks(p, rq);
> +
>  	list_del(&p->run_list);
>  	if (list_empty(array->queue + p->prio))
>  		__clear_bit(p->prio, array->bitmap);


  reply	other threads:[~2007-07-11 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 14:47 [Patch RT] Fix CFS load balancing for RT tasks Sébastien Dugué
2007-07-11 17:06 ` Thomas Gleixner [this message]
2007-07-11 17:41   ` Steven Rostedt
2007-07-12  6:56     ` Sébastien Dugué
2007-07-12  6:28   ` Sébastien Dugué
2007-07-12 16:41 ` Josh Triplett
2007-07-12 17:13   ` Josh Triplett
2007-07-13  7:01     ` Sébastien Dugué
2007-07-13  6:54   ` Sébastien Dugué

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=1184173580.12353.105.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=Gilles.Carry@ext.bull.net \
    --cc=dvhltc@us.ibm.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sebastien.dugue@bull.net \
    /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