All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	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 16:08:11 +0100	[thread overview]
Message-ID: <20191125150811.GA116487@gmail.com> (raw)
In-Reply-To: <9af8a5eb-5104-ad0b-bf46-dedb65d66a07@arm.com>


* Valentin Schneider <valentin.schneider@arm.com> wrote:

> 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.

I really didn't want to do an intrusive rebasing of the Git tree though, 
especially as we didn't know whether the improvements a) improved things 
b) were stable:

> > 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])

We can give testers a linearized tree for testing, should this come up 
(which I doubt it will ...), ok?

Thanks,

	Ingo

  reply	other threads:[~2019-11-25 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 12:59 [GIT PULL] scheduler changes for v5.5 Ingo Molnar
2019-11-25 13:49 ` Valentin Schneider
2019-11-25 15:08   ` Ingo Molnar [this message]
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=20191125150811.GA116487@gmail.com \
    --to=mingo@kernel.org \
    --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=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=valentin.schneider@arm.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 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.