mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: "'Vincent Guittot'" <vincent.guittot@linaro.org>
Cc: "'Wanpeng Li'" <kernellwp@gmail.com>,
	"'Peter Zijlstra'" <peterz@infradead.org>,
	"'Ingo Molnar'" <mingo@kernel.org>,
	"'linux-kernel'" <linux-kernel@vger.kernel.org>,
	"'Preeti U Murthy'" <preeti@linux.vnet.ibm.com>,
	"'Morten Rasmussen'" <Morten.Rasmussen@arm.com>,
	"'Kamalesh Babulal'" <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH v8 03/10] sched: move cfs task on a CPU with higher capacity
Date: Tue, 04 Nov 2014 20:07:44 +0800	[thread overview]
Message-ID: <011001cff827$f14b9870$d3e2c950$@alibaba-inc.com> (raw)

> >>   +     /*
> >> +        * The dst_cpu is idle and the src_cpu CPU has only 1 CFS task.
> >
> >
> > Why specify one task instead of not less than one?
> 
> if cfs.h_nr_running = 0 (which should not occurs at that point), we
> don't need to do more test to check if it's worth moving the task
> because there is no task to move.
> 
I wonder if you can please shed light on the case that 
the dst_cpu is newly idle.

Thanks
Hillf


             reply	other threads:[~2014-11-04 12:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 12:07 Hillf Danton [this message]
2014-11-04 12:48 ` Vincent Guittot
2014-11-04 12:54   ` Hillf Danton
2014-11-04 13:10     ` Vincent Guittot
2014-11-04 13:31       ` Hillf Danton
2014-11-04 16:45         ` Vincent Guittot
  -- strict thread matches above, loose matches on Subject: below --
2014-10-31  8:47 [PATCH v8 00/10] sched: consolidation of CPU capacity and usage Vincent Guittot
2014-10-31  8:47 ` [PATCH v8 03/10] sched: move cfs task on a CPU with higher capacity Vincent Guittot
2014-11-04  8:30   ` Wanpeng Li
2014-11-04  9:41     ` Vincent Guittot
2014-11-04 10:42       ` Wanpeng Li
2014-11-04 11:10         ` Vincent Guittot
2014-11-18 10:47   ` Wanpeng Li
2014-11-18 11:00     ` Vincent Guittot

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='011001cff827$f14b9870$d3e2c950$@alibaba-inc.com' \
    --to=hillf.zj@alibaba-inc.com \
    --cc=Morten.Rasmussen@arm.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=kernellwp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=preeti@linux.vnet.ibm.com \
    --cc=vincent.guittot@linaro.org \
    /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
Powered by JetHome