From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, virtualization@lists.linux.dev,
linux-nvme@lists.infradead.org
Subject: Re: [linus:master] [block] e70c301fae: stress-ng.aiol.ops_per_sec 49.6% regression
Date: Tue, 17 Dec 2024 05:55:28 +0100 [thread overview]
Message-ID: <20241217045527.GA16091@lst.de> (raw)
In-Reply-To: <20241213143224.GA16111@lst.de>
On Fri, Dec 13, 2024 at 03:32:24PM +0100, Christoph Hellwig wrote:
> On Thu, Dec 12, 2024 at 09:51:45PM +0800, kernel test robot wrote:
> >
> >
> > Hello,
> >
> > kernel test robot noticed a 49.6% regression of stress-ng.aiol.ops_per_sec on:
>
> This sounds like there is some other I/O path that still reorders,
> which got messed up. What storage driver is this using? The repro
> material talks about an ata disk, but I'm still curious if it's ahci
> or some other driver, or a SAS HBA?
Do you have the information on what hardware is used for this test?
next prev parent reply other threads:[~2024-12-17 4:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 13:51 [linus:master] [block] e70c301fae: stress-ng.aiol.ops_per_sec 49.6% regression kernel test robot
2024-12-13 14:32 ` Christoph Hellwig
2024-12-17 4:55 ` Christoph Hellwig [this message]
2024-12-17 6:55 ` Oliver Sang
2024-12-17 6:56 ` Christoph Hellwig
2025-01-02 9:49 ` Niklas Cassel
2025-01-03 6:49 ` Christoph Hellwig
2025-01-03 9:09 ` Niklas Cassel
2025-01-06 7:21 ` Christoph Hellwig
2025-01-07 8:27 ` Oliver Sang
2025-01-08 10:39 ` Niklas Cassel
2025-01-10 6:53 ` Oliver Sang
2025-01-15 11:42 ` Niklas Cassel
2025-01-16 6:37 ` Oliver Sang
2025-01-16 10:04 ` Niklas Cassel
2025-01-14 6:45 ` Oliver Sang
2025-01-07 8:26 ` 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=20241217045527.GA16091@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=virtualization@lists.linux.dev \
/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).