All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [RFC/PATCH] sched: Honor sync wake up in select_idle_sibling
Date: Fri, 10 Aug 2012 10:14:44 +0200	[thread overview]
Message-ID: <1344586484.4330.24.camel@marge.simpson.net> (raw)
In-Reply-To: <1344583512-25352-1-git-send-email-namhyung@kernel.org>

On Fri, 2012-08-10 at 16:25 +0900, Namhyung Kim wrote: 
> From: Namhyung Kim <namhyung.kim@lge.com>
> 
> When sync wakeup happens and there's the waker task running alone,
> select the target cpu as if it's already idle.

Ouch.  That defeats the purpose of select_idle_sibling().  Just because
we're doing a sync wakeup does not mean there's no convertible overlap,
nor that the waker is really really going to take a nap immediately.  A
lot of the places that benefit up to and including hugely from looking
for an idle shared cache to wake to do sync wakeups.

> Cc: Mike Galbraith <efault@gmx.de>
> Cc: Suresh Siddha <suresh.b.siddha@intel.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
>  kernel/sched/fair.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index d0cc03b3e70b..64b68bc82b52 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -2632,7 +2632,7 @@ find_idlest_cpu(struct sched_group *group, struct task_struct *p, int this_cpu)
>  /*
>   * Try and locate an idle CPU in the sched_domain.
>   */
> -static int select_idle_sibling(struct task_struct *p, int target)
> +static int select_idle_sibling(struct task_struct *p, int target, int sync)
>  {
>  	int cpu = smp_processor_id();
>  	int prev_cpu = task_cpu(p);
> @@ -2646,6 +2646,13 @@ static int select_idle_sibling(struct task_struct *p, int target)
>  		return cpu;
>  
>  	/*
> +	 * If the task is going to be woken-up on this cpu and there's only
> +	 * the sync-waker running, then it is the right target.
> +	 */
> +	if (target == cpu && sync && this_rq()->nr_running == 1)
> +		return cpu;
> +
> +	/*
>  	 * If the task is going to be woken-up on the cpu where it previously
>  	 * ran and if it is currently idle, then it the right target.
>  	 */
> @@ -2748,7 +2755,7 @@ select_task_rq_fair(struct task_struct *p, int sd_flag, int wake_flags)
>  		if (cpu == prev_cpu || wake_affine(affine_sd, p, sync))
>  			prev_cpu = cpu;
>  
> -		new_cpu = select_idle_sibling(p, prev_cpu);
> +		new_cpu = select_idle_sibling(p, prev_cpu, sync);
>  		goto unlock;
>  	}
>  



  reply	other threads:[~2012-08-10  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  7:25 [RFC/PATCH] sched: Honor sync wake up in select_idle_sibling Namhyung Kim
2012-08-10  8:14 ` Mike Galbraith [this message]
2012-08-10  8:51   ` Namhyung Kim

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=1344586484.4330.24.camel@marge.simpson.net \
    --to=efault@gmx.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=suresh.b.siddha@intel.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.