All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Mike Galbraith <efault@gmx.de>,
	Michael Wang <wangyun@linux.vnet.ibm.com>
Subject: Re: [PATCH] sched: Skip looking at skip if next or last is set
Date: Thu, 21 Feb 2013 21:36:13 +0530	[thread overview]
Message-ID: <20130221160613.GA18617@linux.vnet.ibm.com> (raw)
In-Reply-To: <1361349985.10155.1.camel@laptop>

* Peter Zijlstra <peterz@infradead.org> [2013-02-20 09:46:25]:

> On Mon, 2013-02-18 at 18:31 +0530, Srikar Dronamraju wrote:
> > pick_next_entity() prefers next, then last. However code checks if the
> > left entity can be skipped even if next / last is set.
> > 
> > Check if left entity should be skipped only if next/last is not set.
> 
> You fail to explain why its a problem and continue to make a horrid mess
> of the code..
> 

If we look at the comments above pick_next_entity(),  it states:
/*
 * Pick the next process, keeping these things in mind, in this order:
 * 1) keep things fair between processes/task groups
 * 2) pick the "next" process, since someone really wants that to run
 * 3) pick the "last" process, for cache locality
 * 4) do not run the "skip" process, if something else is available
 */ 

Currently the code checks in the reverse order, though the preference is
correctly maintained as listed in comments.  But in some cases, we might be
doing redundant checks.  Lets assume next is set, then we should avoid 
checking for skip, last and their fairness with left.

So what I intended to do was change the order, i.e check for last only if next
is not set (or was picking next was unfair wrt left) and check for "something
else (second from left)" if last is not set (or picking last was unfair wrt
left).

However after sending the patch, I stumbled across these links.
https://lkml.org/lkml/2012/1/16/500 and https://lkml.org/lkml/2012/1/25/195

> > Signed-off-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> > ---
> >  kernel/sched/fair.c |   31 +++++++++++++++----------------
> >  1 files changed, 15 insertions(+), 16 deletions(-)
> > 
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index fdee793..cc97b12 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -1900,27 +1900,26 @@ static struct sched_entity *pick_next_entity(struct cfs_rq *cfs_rq)
> >  	struct sched_entity *left = se;
> >  
> >  	/*
> > -	 * Avoid running the skip buddy, if running something else can
> > -	 * be done without getting too unfair.
> > +	 * Someone really wants next to run. If it's not unfair, run it.
> >  	 */
> > -	if (cfs_rq->skip == se) {
> > -		struct sched_entity *second = __pick_next_entity(se);
> > +	if (cfs_rq->next && wakeup_preempt_entity(cfs_rq->next, left) < 1) {
> > +		se = cfs_rq->next;
> > +	} else if (cfs_rq->last && wakeup_preempt_entity(cfs_rq->last, left) < 1) {
> > +		/*
> > +		 * Prefer last buddy, try to return the CPU to a preempted
> > +		 * task.
> > +		 */
> > +		se = cfs_rq->last;
> > +	} else if (cfs_rq->skip == left) {
> > +		/*
> > +		 * Avoid running the skip buddy, if running something else
> > +		 * can be done without getting too unfair.
> > +		 */
> > +		struct sched_entity *second = __pick_next_entity(left);
> >  		if (second && wakeup_preempt_entity(second, left) < 1)
> >  			se = second;
> >  	}
> >  
> > -	/*
> > -	 * Prefer last buddy, try to return the CPU to a preempted task.
> > -	 */
> > -	if (cfs_rq->last && wakeup_preempt_entity(cfs_rq->last, left) < 1)
> > -		se = cfs_rq->last;
> > -
> > -	/*
> > -	 * Someone really wants this to run. If it's not unfair, run it.
> > -	 */
> > -	if (cfs_rq->next && wakeup_preempt_entity(cfs_rq->next, left) < 1)
> > -		se = cfs_rq->next;
> > -
> >  	clear_buddies(cfs_rq, se);
> >  
> >  	return se;
> > 
> 
> 

-- 
Thanks and Regards
Srikar Dronamraju


  reply	other threads:[~2013-02-21 16:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 13:01 [PATCH] sched: Skip looking at skip if next or last is set Srikar Dronamraju
2013-02-20  8:46 ` Peter Zijlstra
2013-02-21 16:06   ` Srikar Dronamraju [this message]
2013-02-22  3:06     ` Michael Wang

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=20130221160613.GA18617@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=wangyun@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 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.