From: Jens Axboe <[email protected]>
To: kernel test robot <[email protected]>
Cc: LKML <[email protected]>,
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [io_uring] 584b0180f0: phoronix-test-suite.fio.SequentialWrite.IO_uring.Yes.Yes.1MB.DefaultTestDirectory.mb_s -10.2% regression
Date: Fri, 27 May 2022 07:50:27 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20220527092432.GE11731@xsang-OptiPlex-9020>
On 5/27/22 3:24 AM, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed a -10.2% regression of phoronix-test-suite.fio.SequentialWrite.IO_uring.Yes.Yes.1MB.DefaultTestDirectory.mb_s due to commit:
>
>
> commit: 584b0180f0f4d67d7145950fe68c625f06c88b10 ("io_uring: move read/write file prep state into actual opcode handler")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: phoronix-test-suite
> on test machine: 96 threads 2 sockets Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz with 512G memory
> with following parameters:
>
> test: fio-1.14.1
> option_a: Sequential Write
> option_b: IO_uring
> option_c: Yes
> option_d: Yes
> option_e: 1MB
> option_f: Default Test Directory
> cpufreq_governor: performance
> ucode: 0x500320a
>
> test-description: The Phoronix Test Suite is the most comprehensive testing and benchmarking platform available that provides an extensible framework for which new tests can be easily added.
> test-url: http://www.phoronix-test-suite.com/
I'm a bit skeptical on this, but I'd like to try and run the test case.
Since it's just a fio test case, why can't I find it somewhere? Seems
very convoluted to have to setup lkp-tests just for this. Besides, I
tried, but it doesn't work on aarch64...
--
Jens Axboe
next parent reply other threads:[~2022-05-27 13:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220527092432.GE11731@xsang-OptiPlex-9020>
2022-05-27 13:50 ` Jens Axboe [this message]
2022-06-08 8:00 ` [io_uring] 584b0180f0: phoronix-test-suite.fio.SequentialWrite.IO_uring.Yes.Yes.1MB.DefaultTestDirectory.mb_s -10.2% regression Oliver Sang
2022-06-14 1:54 ` [LKP] " Yin Fengwei
2022-07-12 8:06 ` Yin Fengwei
2022-07-15 15:58 ` Jens Axboe
2022-07-18 0:58 ` Yin Fengwei
2022-07-18 1:14 ` Jens Axboe
2022-07-18 3:30 ` Yin Fengwei
2022-07-18 16:27 ` Jens Axboe
2022-07-19 0:27 ` Yin Fengwei
2022-07-19 2:16 ` Yin Fengwei
2022-07-19 2:29 ` Jens Axboe
2022-07-19 8:58 ` Yin Fengwei
2022-07-20 17:24 ` Jens Axboe
2022-07-20 18:13 ` Jens Axboe
2022-07-20 23:25 ` Yin Fengwei
2022-07-21 2:59 ` Yin Fengwei
2022-07-21 3:08 ` Yin Fengwei
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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