From: Yonghong Song <yhs@fb.com>
To: kernel test robot <oliver.sang@intel.com>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
<lkp@lists.01.org>, <lkp@intel.com>, <ying.huang@intel.com>,
<feng.tang@intel.com>, <zhengjun.xing@linux.intel.com>
Subject: Re: [bpf] b89fbfbb85: netperf.Throughput_tps -21.3% regression
Date: Thu, 19 Aug 2021 23:29:27 -0700 [thread overview]
Message-ID: <449d7b62-9339-2d1f-1798-2150e2764063@fb.com> (raw)
In-Reply-To: <20210820055009.GA29369@xsang-OptiPlex-9020>
On 8/19/21 10:50 PM, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a -21.3% regression of netperf.Throughput_tps due to commit:
>
>
> commit: b89fbfbb854c9afc3047e8273cc3a694650b802e ("bpf: Implement minimal BPF perf link")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
Could you do a test again to double check?
The above patch is related to bpf perf_event area.
It should not have any impact with netperf.
>
>
> in testcase: netperf
> on test machine: 192 threads 4 sockets Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz with 192G memory
> with following parameters:
>
> ip: ipv4
> runtime: 300s
> nr_threads: 16
> cluster: cs-localhost
> test: TCP_CRR
> cpufreq_governor: performance
> ucode: 0x5003006
>
> test-description: Netperf is a benchmark that can be use to measure various aspect of networking performance.
> test-url: http://www.netperf.org/netperf/
>
>
>
[...]
next prev parent reply other threads:[~2021-08-20 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 5:50 [bpf] b89fbfbb85: netperf.Throughput_tps -21.3% regression kernel test robot
2021-08-20 6:29 ` Yonghong Song [this message]
2021-09-02 8:35 ` [LKP] " Si, Beibei
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=449d7b62-9339-2d1f-1798-2150e2764063@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=daniel@iogearbox.net \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=ying.huang@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 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).