From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Andreas Hindborg <andreas.hindborg@wdc.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, ming.lei@redhat.com
Subject: Re: Reordering of ublk IO requests
Date: Mon, 21 Nov 2022 16:13:10 +0800 [thread overview]
Message-ID: <Y3szFl5VcD/MNDu5@T590> (raw)
In-Reply-To: <Y3swtrdPaI5lGMpj@infradead.org>
On Mon, Nov 21, 2022 at 12:03:02AM -0800, Christoph Hellwig wrote:
> I've been wading through this thread a bit, and while I can't follow
> everything due some pretty bad reply trimming I'm really really
> confused by this whole discussion.
>
> Every single storage system, be that hard drives, SSDs, file systems
> or what else much preferres sequential write. Any code that turns
> perfectly sequential writes into reverse sequential writes is a massive
> performance bug, zoned or not.
>
> So totally independent of zone device support in ublk this needs to be
> fixed ASAP.
I will send one fix soon.
BTW, blk-mq has such similar issue, which is reported for while, but
not addressed yet.
https://lore.kernel.org/linux-nvme/CAHex0coMNvFa1TPzK+5mZHsiie4d1Jd0Z8ejcZk1Vi1_4F7eRg@mail.gmail.com/T/#mbcb9b52ff61aed6fdd1b6630c6e62e55a4ed898f
Thanks,
Ming
next prev parent reply other threads:[~2022-11-21 8:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 15:00 Reordering of ublk IO requests Andreas Hindborg
2022-11-17 2:18 ` Ming Lei
2022-11-17 8:05 ` Andreas Hindborg
2022-11-17 8:52 ` Ming Lei
2022-11-17 9:07 ` Andreas Hindborg
2022-11-17 11:47 ` Ming Lei
2022-11-17 11:59 ` Andreas Hindborg
2022-11-17 13:11 ` Damien Le Moal
2022-11-17 13:31 ` Andreas Hindborg
2022-11-18 1:51 ` Damien Le Moal
2022-11-18 9:29 ` Andreas Hindborg
2022-11-18 4:12 ` Ming Lei
2022-11-18 4:35 ` Damien Le Moal
2022-11-18 6:07 ` Ming Lei
2022-11-18 9:41 ` Andreas Hindborg
2022-11-18 11:28 ` Ming Lei
2022-11-18 11:49 ` Andreas Hindborg
2022-11-18 12:46 ` Andreas Hindborg
2022-11-18 12:47 ` Ming Lei
2022-11-19 0:24 ` Damien Le Moal
2022-11-19 7:36 ` Andreas Hindborg
2022-11-21 10:15 ` Andreas Hindborg
2022-11-20 14:37 ` Ming Lei
2022-11-21 1:25 ` Damien Le Moal
2022-11-21 8:03 ` Christoph Hellwig
2022-11-21 8:13 ` Ming Lei [this message]
2022-11-17 13:00 ` Damien Le Moal
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=Y3szFl5VcD/MNDu5@T590 \
--to=ming.lei@redhat.com \
--cc=andreas.hindborg@wdc.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
/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).