public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: ego@in.ibm.com
Cc: Gregory Haskins <ghaskins@novell.com>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
	Balbir Singh <balbir@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [PATCH] sched: Fix __load_balance_iterator() for cfq with only one task
Date: Fri, 05 Sep 2008 17:13:48 +0200	[thread overview]
Message-ID: <1220627628.11202.16.camel@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20080905123004.GD6238@in.ibm.com>

On Fri, 2008-09-05 at 18:00 +0530, Gautham R Shenoy wrote:
> sched: Fix __load_balance_iterator() for cfq with only one task.
> 
> From: Gautham R Shenoy <ego@in.ibm.com>
> 
> The __load_balance_iterator() returns a NULL when there's only one
> sched_entity which is a task. It is caused by the following code-path.
> 
> 
> 	/* Skip over entities that are not tasks */
> 	do {
> 		se = list_entry(next, struct sched_entity, group_node);
> 		next = next->next;
> 	} while (next != &cfs_rq->tasks && !entity_is_task(se));
> 
> 	if (next == &cfs_rq->tasks)
> 		return NULL;
> 	^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>       This will return NULL even when se is a task.
> 
> As a side-effect, there was a regression in sched_mc behavior since 2.6.25,
> since iter_move_one_task() when it calls load_balance_start_fair(),
> would not get any tasks to move!
> 
> Fix this by checking if the last entity was a task or not.

Gregory did a similar fix a while ago, but that caused grief of some
kind..

Greg, can you recollect why we pulled it? I can't seem to find it.

Aside from that this patch looks fine..

> Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> ---
> 
>  kernel/sched_fair.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> 
> diff --git a/kernel/sched_fair.c b/kernel/sched_fair.c
> index fb8994c..f1c96e3 100644
> --- a/kernel/sched_fair.c
> +++ b/kernel/sched_fair.c
> @@ -1451,7 +1451,7 @@ __load_balance_iterator(struct cfs_rq *cfs_rq, struct list_head *next)
>  		next = next->next;
>  	} while (next != &cfs_rq->tasks && !entity_is_task(se));
>  
> -	if (next == &cfs_rq->tasks)
> +	if (next == &cfs_rq->tasks && !entity_is_task(se))
>  		return NULL;
>  
>  	cfs_rq->balance_iterator = next;


  reply	other threads:[~2008-09-05 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05 12:30 [PATCH] sched: Fix __load_balance_iterator() for cfq with only one task Gautham R Shenoy
2008-09-05 15:13 ` Peter Zijlstra [this message]
2008-09-05 17:23   ` Peter Zijlstra
2008-09-12  6:35     ` Gautham R Shenoy
2008-09-12  6:56       ` Peter Zijlstra
2008-09-12  7:05       ` Mike Galbraith
2008-09-12 10:57       ` Mike Galbraith
2008-09-12 11:07         ` Gautham R Shenoy
2008-09-12 15:52 ` Chris Friesen

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=1220627628.11202.16.camel@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=balbir@in.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=svaidy@linux.vnet.ibm.com \
    /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