From: Mel Gorman <mgorman@techsingularity.net>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Phil Auld <pauld@redhat.com>,
Peter Puhov <peter.puhov@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Robert Foley <robert.foley@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Jirka Hladky <jhladky@redhat.com>
Subject: Re: [PATCH v1] sched/fair: update_pick_idlest() Select group with lowest group_util when idle_cpus are equal
Date: Fri, 6 Nov 2020 17:02:27 +0000 [thread overview]
Message-ID: <20201106170227.GG3371@techsingularity.net> (raw)
In-Reply-To: <CAKfTPtCzN934zZ5LzP0pv9iMocwjqoH17a=J5RS0OjT9GMFRMw@mail.gmail.com>
On Fri, Nov 06, 2020 at 05:06:59PM +0100, Vincent Guittot wrote:
> > > > While it was clear-cut for 5.9, it's less clear-cut for 5.10-rc2 although
> > > > the gitsource shows some severe differences depending on the machine that
> > > > is worth being extremely cautious about. I would still prefer a revert
> > > > but I'm also extremely biased and I know there are other patches in the
> > >
> > > This one from Julia can also impact
> > >
> >
> > Which one? I'm guessing "[PATCH v2] sched/fair: check for idle core"
>
> Yes, Sorry I sent my answer before adding the link
>
Grand, that's added to the mix on top to see how both patches measure up
versus a revert. No guarantee I'll have full results by Monday. As usual,
the test grid is loaded up to the eyeballs.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2020-11-06 17:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:59 [PATCH v1] sched/fair: update_pick_idlest() Select group with lowest group_util when idle_cpus are equal peter.puhov
2020-07-22 9:12 ` [tip: sched/core] " tip-bot2 for Peter Puhov
2020-11-02 10:50 ` [PATCH v1] " Mel Gorman
2020-11-02 11:06 ` Vincent Guittot
2020-11-02 14:44 ` Phil Auld
2020-11-02 16:52 ` Mel Gorman
2020-11-04 9:42 ` Mel Gorman
2020-11-04 10:06 ` Vincent Guittot
2020-11-04 10:47 ` Mel Gorman
2020-11-04 11:34 ` Vincent Guittot
2020-11-06 12:03 ` Mel Gorman
2020-11-06 13:33 ` Vincent Guittot
2020-11-06 16:00 ` Mel Gorman
2020-11-06 16:06 ` Vincent Guittot
2020-11-06 17:02 ` Mel Gorman [this message]
2020-11-09 15:24 ` Phil Auld
2020-11-09 15:38 ` Mel Gorman
2020-11-09 15:47 ` Phil Auld
2020-11-09 15:49 ` Vincent Guittot
2020-11-10 14:05 ` Mel Gorman
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=20201106170227.GG3371@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jhladky@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peter.puhov@linaro.org \
--cc=peterz@infradead.org \
--cc=robert.foley@linaro.org \
--cc=rostedt@goodmis.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 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.