From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: linux-block@vger.kernel.org, virtualization@lists.linux.dev,
linux-nvme@lists.infradead.org
Subject: Re: [Report] requests are submitted to hardware in reverse order from nvme/virtio-blk queue_rqs()
Date: Fri, 26 Jan 2024 06:10:23 -0800 [thread overview]
Message-ID: <ZbO9T_R4lN_7WkwQ@infradead.org> (raw)
In-Reply-To: <ZbD7ups50ryrlJ/G@fedora>
On Wed, Jan 24, 2024 at 07:59:54PM +0800, Ming Lei wrote:
> Hello,
>
> Requests are added to plug list in reverse order, and both virtio-blk
> and nvme retrieves request from plug list in order, so finally requests
> are submitted to hardware in reverse order via nvme_queue_rqs() or
> virtio_queue_rqs, see:
> May this reorder be one problem for virtio-blk and nvme-pci?
It it isn't really a problem for the drivers, but de-serializing
I/O patterns tends to be not good. I know at least a couple cases
where this would hurt:
- SSDs with sequential write detection
- zoned SSDs with zoned append, as this now turns a sequential
user write pattern into one that is fairly random
- HDDs much prefer real sequential I/O, although until nvme HDDs
go beyong the prototype stage that's probably not hitting this
case yet
So yes, we should fix this.
>
>
> Thanks,
> Ming
>
>
---end quoted text---
next prev parent reply other threads:[~2024-01-26 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 11:59 [Report] requests are submitted to hardware in reverse order from nvme/virtio-blk queue_rqs() Ming Lei
2024-01-24 15:41 ` Keith Busch
2024-01-24 22:32 ` Damien Le Moal
2024-01-25 4:23 ` Ming Lei
2024-01-25 15:33 ` Jens Axboe
2024-01-26 14:10 ` Christoph Hellwig [this message]
2024-10-07 22:39 ` Bart Van Assche
2024-10-08 11:33 ` Christoph Hellwig
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=ZbO9T_R4lN_7WkwQ@infradead.org \
--to=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.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