From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Max Kellermann <max.kellermann@ionos.com>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [drivers/char/mem] 1b057bd800: stress-ng.splice.ops_per_sec -99.8% regression
Date: Tue, 17 Oct 2023 18:56:56 +0200 [thread overview]
Message-ID: <2023101759-front-ember-6354@gregkh> (raw)
In-Reply-To: <202310172247.b9959bd4-oliver.sang@intel.com>
On Tue, Oct 17, 2023 at 11:06:42PM +0800, kernel test robot wrote:
>
>
> Hello,
>
> kernel test robot noticed a -99.8% regression of stress-ng.splice.ops_per_sec on:
>
>
> commit: 1b057bd800c3ea0c926191d7950cd2365eddc9bb ("drivers/char/mem: implement splice() for /dev/zero, /dev/full")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> testcase: stress-ng
> test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G memory
> parameters:
>
> nr_threads: 100%
> testtime: 60s
> class: pipe
> test: splice
> cpufreq_governor: performance
>
>
> In addition to that, the commit also has significant impact on the following tests:
>
> +------------------+-------------------------------------------------------------------------------------------------+
> | testcase: change | stress-ng: stress-ng.splice.ops_per_sec 38.9% improvement |
So everything now goes faster, right? -99.8% regression means 99.8%
faster?
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-17 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 15:06 kernel test robot
2023-10-17 16:56 ` Greg Kroah-Hartman [this message]
2023-10-18 6:31 ` Max Kellermann
2023-10-18 7:07 ` Oliver Sang
2023-10-18 7:57 ` Greg Kroah-Hartman
2023-10-18 8:12 ` Max Kellermann
2023-10-18 10:01 ` Max Kellermann
[not found] ` <CAKPOu+_T8xk4yd2P4KT4j3eMoFqwYmkxqDHaFtv4Hii5-XyPuA@mail.gmail.com>
2023-10-18 11:12 ` Max Kellermann
2023-10-19 5:41 ` Oliver Sang
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=2023101759-front-ember-6354@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=max.kellermann@ionos.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=ying.huang@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