From: Aubrey Li <aubrey.intel@gmail.com>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Aubrey Li <aubrey.li@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
dietmar.eggemann@arm.com, Steven Rostedt <rostedt@goodmis.org>,
bsegall@google.com, mgorman@suse.de,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
Vineeth Remanan Pillai <vpillai@digitalocean.com>,
Joel Fernandes <joel@joelfernandes.org>,
Aubrey Li <aubrey.li@linux.intel.com>,
lkp@lists.01.org
Subject: Re: [sched/fair] 59901cb452: netperf.Throughput_Mbps -27.3% regression
Date: Sun, 29 Mar 2020 12:26:41 +0800 [thread overview]
Message-ID: <CAERHkrukPEO_sCiOS_YWnVPvFrHUbL10oov6hd_UVZ9PdvchkQ@mail.gmail.com> (raw)
In-Reply-To: <20200328132325.GC11705@shao2-debian>
On Sat, Mar 28, 2020 at 9:24 PM kernel test robot <rong.a.chen@intel.com> wrote:
>
> Greeting,
>
> FYI, we noticed a -27.3% regression of netperf.Throughput_Mbps due to commit:
>
>
> commit: 59901cb4520c44bfce81f523bc61e7284a931ad1 ("[PATCH] sched/fair: Don't pull task if local group is more loaded than busiest group")
Thanks for the report, Robot, ;-)
This patch is abandoned, and replaced by another one:
- [PATCH] sched/fair: Fix negative imbalance in imbalance calculation
Thanks,
-Aubrey
prev parent reply other threads:[~2020-03-29 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 12:46 [PATCH] sched/fair: Don't pull task if local group is more loaded than busiest group Aubrey Li
2020-03-25 13:43 ` Phil Auld
2020-03-26 1:51 ` Li, Aubrey
2020-03-25 13:58 ` Vincent Guittot
2020-03-26 1:57 ` Li, Aubrey
2020-03-28 13:23 ` [sched/fair] 59901cb452: netperf.Throughput_Mbps -27.3% regression kernel test robot
2020-03-29 4:26 ` Aubrey Li [this message]
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=CAERHkrukPEO_sCiOS_YWnVPvFrHUbL10oov6hd_UVZ9PdvchkQ@mail.gmail.com \
--to=aubrey.intel@gmail.com \
--cc=aubrey.li@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rong.a.chen@intel.com \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vpillai@digitalocean.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).