From: Valentin Schneider <valentin.schneider@arm.com>
To: Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Mel Gorman <mgorman@suse.de>, Ben Segall <bsegall@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [GIT PULL] scheduler changes for v5.5
Date: Mon, 25 Nov 2019 13:49:38 +0000 [thread overview]
Message-ID: <9af8a5eb-5104-ad0b-bf46-dedb65d66a07@arm.com> (raw)
In-Reply-To: <20191125125944.GA22218@gmail.com>
On 25/11/2019 12:59, Ingo Molnar wrote:
So I really don't want to be labeled as "that annoying scheduler PR guy",
but some patches in Vincent's rework should be squashed to avoid being
performance bisection honeypots.
> Vincent Guittot (14):
> sched/fair: Remove meaningless imbalance calculation
> sched/fair: Rework load_balance()
These two ^ (were split for ease of reviewing, [1])
> sched/fair: Rework find_idlest_group()
> sched/fair: Fix rework of find_idlest_group()
And these two ^ (Mel voiced similar concerns at [2])
Sorry for being annoying :/
[1]: https://lore.kernel.org/lkml/CAKfTPtCqLGJDNHgG099wQ7Gy6A+63yP36cxAR_somNPEcJMxGA@mail.gmail.com/
[2]: https://lore.kernel.org/lkml/20191030160749.GN3016@techsingularity.net/
next prev parent reply other threads:[~2019-11-25 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 12:59 Ingo Molnar
2019-11-25 13:49 ` Valentin Schneider [this message]
2019-11-25 15:08 ` Ingo Molnar
2019-11-25 16:20 ` Valentin Schneider
2019-11-25 16:34 ` Mel Gorman
2019-11-25 16:48 ` Linus Torvalds
2019-11-25 16:50 ` Valentin Schneider
2019-11-26 23:25 ` Linus Torvalds
2019-11-27 1:30 ` pr-tracker-bot
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=9af8a5eb-5104-ad0b-bf46-dedb65d66a07@arm.com \
--to=valentin.schneider@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®