From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Mel Gorman <mgorman@techsingularity.net>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com,
ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@linux.intel.com, aubrey.li@linux.intel.com,
yu.c.chen@intel.com
Subject: Re: [sched/fair] 56498cfb04: netperf.Throughput_tps -5.4% regression
Date: Wed, 22 Sep 2021 14:44:00 +0200 [thread overview]
Message-ID: <20210922124400.GQ4323@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20210912153447.GG25450@xsang-OptiPlex-9020>
On Sun, Sep 12, 2021 at 11:34:47PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a -5.4% regression of netperf.Throughput_tps due to commit:
>
>
> commit: 56498cfb045d7147cdcba33795d19429afcd1d00 ("sched/fair: Avoid a second scan of target in select_idle_cpu")
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
Mel, was this in line with your own benchmarks?
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [sched/fair] 56498cfb04: netperf.Throughput_tps -5.4% regression
Date: Wed, 22 Sep 2021 14:44:00 +0200 [thread overview]
Message-ID: <20210922124400.GQ4323@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20210912153447.GG25450@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
On Sun, Sep 12, 2021 at 11:34:47PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a -5.4% regression of netperf.Throughput_tps due to commit:
>
>
> commit: 56498cfb045d7147cdcba33795d19429afcd1d00 ("sched/fair: Avoid a second scan of target in select_idle_cpu")
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
Mel, was this in line with your own benchmarks?
next prev parent reply other threads:[~2021-09-22 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 15:34 [sched/fair] 56498cfb04: netperf.Throughput_tps -5.4% regression kernel test robot
2021-09-12 15:34 ` kernel test robot
2021-09-22 12:44 ` Peter Zijlstra [this message]
2021-09-22 12:44 ` Peter Zijlstra
2021-09-22 13:42 ` Mel Gorman
2021-09-22 13:42 ` Mel Gorman
2021-09-22 14:31 ` Peter Zijlstra
2021-09-22 14:31 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2021-08-18 15:03 kernel test robot
2021-08-18 15:03 ` kernel test robot
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=20210922124400.GQ4323@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aubrey.li@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=mgorman@techsingularity.net \
--cc=oliver.sang@intel.com \
--cc=x86@kernel.org \
--cc=ying.huang@intel.com \
--cc=yu.c.chen@intel.com \
--cc=zhengjun.xing@linux.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.