From: Peter Zijlstra <peterz@infradead.org>
To: Mel Gorman <mgorman@suse.de>
Cc: kernel test robot <rong.a.chen@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@surriel.com>,
Ben Segall <bsegall@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com, ying.huang@intel.com,
feng.tang@intel.com, zhengjun.xing@intel.com,
aubrey.li@linux.intel.com, yu.c.chen@intel.com
Subject: Re: [sched/fair] fcf0553db6: netperf.Throughput_Mbps -30.8% regression
Date: Mon, 5 Oct 2020 08:51:01 +0200 [thread overview]
Message-ID: <20201005065101.GE2628@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20201004162108.GC3165@suse.de>
On Sun, Oct 04, 2020 at 05:21:08PM +0100, Mel Gorman wrote:
> On Sun, Oct 04, 2020 at 09:27:16PM +0800, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed a -30.8% regression of netperf.Throughput_Mbps due to commit:
> >
> >
> > commit: fcf0553db6f4c79387864f6e4ab4a891601f395e ("sched/fair: Remove meaningless imbalance calculation")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
>
> This commit was the start of a series that made large changes to load
> balancing. The series was not bisect-safe and has since been reconciled
> with the NUMA balancing. Any workload with a potential load balancing
> problem has to be checked against the latest kernel to see if the problem
> persists there. If it does, then tip/sched/core should be checked or
> 5.10-rc1 when it comes out as tip has a few more LB changes pending.
What Mel said ;-)
next prev parent reply other threads:[~2020-10-05 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 13:27 [sched/fair] fcf0553db6: netperf.Throughput_Mbps -30.8% regression kernel test robot
2020-10-04 16:21 ` Mel Gorman
2020-10-05 6:51 ` Peter Zijlstra [this message]
2020-10-05 8:04 ` Ingo Molnar
2020-10-05 6:49 ` Peter Zijlstra
2020-10-05 7:12 ` Vincent Guittot
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=20201005065101.GE2628@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aubrey.li@linux.intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=feng.tang@intel.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@surriel.com \
--cc=rong.a.chen@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=ying.huang@intel.com \
--cc=yu.c.chen@intel.com \
--cc=zhengjun.xing@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 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.