From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Yuyang Du <yuyang.du@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, linux-kernel@vger.kernel.org,
bsegall@google.com, pjt@google.com, morten.rasmussen@arm.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com
Subject: Re: [RFC PATCH 1/2] sched: Clean up SD_BALANCE_WAKE flags in sched domain build-up
Date: Thu, 02 Jun 2016 08:44:21 +0200 [thread overview]
Message-ID: <1464849861.3766.52.camel@gmail.com> (raw)
In-Reply-To: <20160601224106.GB18670@intel.com>
On Thu, 2016-06-02 at 06:41 +0800, Yuyang Du wrote:
> Again, agreed, and with this patch, just disable SD_BALANCE_WAKE. :)
Yeah, we pretty much agree on everything.. other than whether you shoul
d be picking on poor defenseless little SD_WAKE_AFFINE or not :^)
-Mike
next prev parent reply other threads:[~2016-06-02 6:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 1:11 [RFC PATCH 0/2] Remove and replace SD_WAKE_AFFINE with SD_BALANCE_WAKE Yuyang Du
2016-05-31 1:11 ` [RFC PATCH 1/2] sched: Clean up SD_BALANCE_WAKE flags in sched domain build-up Yuyang Du
2016-05-31 9:21 ` Peter Zijlstra
2016-05-31 1:31 ` Yuyang Du
2016-05-31 10:41 ` Peter Zijlstra
2016-05-31 18:00 ` Yuyang Du
2016-06-01 5:07 ` Mike Galbraith
2016-06-01 0:01 ` Yuyang Du
2016-06-01 8:32 ` Vincent Guittot
2016-06-01 1:03 ` Yuyang Du
2016-06-01 9:24 ` Vincent Guittot
2016-06-01 19:35 ` Yuyang Du
2016-06-02 6:56 ` Vincent Guittot
2016-06-01 23:19 ` Yuyang Du
2016-06-01 9:36 ` Mike Galbraith
2016-06-01 20:03 ` Yuyang Du
2016-06-02 5:50 ` Mike Galbraith
2016-06-01 22:41 ` Yuyang Du
2016-06-02 6:44 ` Mike Galbraith [this message]
2016-05-31 1:11 ` [RFC PATCH 2/2] sched: Remove SD_WAKE_AFFINE flag and replace it with SD_BALANCE_WAKE Yuyang Du
2016-05-31 9:23 ` Peter Zijlstra
2016-05-31 1:34 ` Yuyang Du
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=1464849861.3766.52.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=vincent.guittot@linaro.org \
--cc=yuyang.du@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).