From: Bart Van Assche <bvanassche@acm.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Linux Memory Management List <linux-mm@kvack.org>,
Jens Axboe <axboe@kernel.dk>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-block@vger.kernel.org, ying.huang@intel.com,
feng.tang@intel.com, fengwei.yin@intel.com
Subject: Re: [linux-next:master] [block/mq] 574e7779cf: fio.write_iops -72.9% regression
Date: Wed, 31 Jan 2024 10:17:09 -0800 [thread overview]
Message-ID: <da4c78c1-a9d4-4a57-9765-2e6c35fa1062@acm.org> (raw)
In-Reply-To: <202401312320.a335db14-oliver.sang@intel.com>
On 1/31/24 07:42, kernel test robot wrote:
> kernel test robot noticed a -72.9% regression of fio.write_iops on:
>
>
> commit: 574e7779cf583171acb5bf6365047bb0941b387c ("block/mq-deadline: use separate insertion lists")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>
> testcase: fio-basic
> test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G memory
> parameters:
>
> runtime: 300s
> disk: 1HDD
> fs: xfs
> nr_task: 100%
> test_size: 128G
> rw: write
> bs: 4k
> ioengine: io_uring
> direct: direct
> cpufreq_governor: performance
The actual test is available in this file:
https://download.01.org/0day-ci/archive/20240131/202401312320.a335db14-oliver.sang@intel.com/repro-script
I haven't found anything in that file for disabling merging. Merging
requests decreases IOPS. Does this perhaps mean that this test is
broken?
Thanks,
Bart.
next prev parent reply other threads:[~2024-01-31 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 15:42 kernel test robot
2024-01-31 18:17 ` Bart Van Assche [this message]
2024-01-31 18:42 ` Jens Axboe
2024-02-01 7:18 ` Oliver Sang
2024-02-01 13:40 ` Jens Axboe
2024-02-01 14:03 ` Oliver Sang
2024-02-01 14:30 ` Jens Axboe
2024-02-01 14:45 ` Oliver Sang
2024-02-09 21:06 ` Jens Axboe
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=da4c78c1-a9d4-4a57-9765-2e6c35fa1062@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=feng.tang@intel.com \
--cc=fengwei.yin@intel.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oleksandr@natalenko.name \
--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