From: Niklas Cassel <cassel@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Oliver Sang <oliver.sang@intel.com>,
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,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [linus:master] [block] e70c301fae: stress-ng.aiol.ops_per_sec 49.6% regression
Date: Thu, 2 Jan 2025 10:49:41 +0100 [thread overview]
Message-ID: <Z3ZhNYHKZPMpv8Cz@ryzen> (raw)
In-Reply-To: <20241217065614.GA19113@lst.de>
Hello Oliver, Christoph,
On Tue, Dec 17, 2024 at 07:56:14AM +0100, Christoph Hellwig wrote:
> On Tue, Dec 17, 2024 at 02:55:23PM +0800, Oliver Sang wrote:
> > from below information, it seems an 'ahci' to me. but since I have limited
> > knowledge about storage driver, maybe I'm wrong. if you want more information,
> > please let us know. thanks a lot!
>
> Yes, this looks like ahci. Thanks a lot!
Did this ever get resolved?
I haven't seen a patch that seems to address this.
AHCI (ata_scsi_queuecmd()) only issues a single command, so if there is any
reordering when issuing a batch of commands, my guess is that the problem
also affects SCSI / the problem is in upper layers above AHCI, i.e. SCSI lib
or block layer.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-01-02 9:49 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
2024-12-17 6:55 ` Oliver Sang
2024-12-17 6:56 ` Christoph Hellwig
2025-01-02 9:49 ` Niklas Cassel [this message]
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=Z3ZhNYHKZPMpv8Cz@ryzen \
--to=cassel@kernel.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--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