From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Damien Le Moal <damien.lemoal@wdc.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Khazhy Kumykov <khazhy@google.com>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [PATCH 2/5] scsi: Retry unaligned zoned writes
Date: Wed, 15 Jun 2022 12:42:07 -0700 [thread overview]
Message-ID: <78ba5207-aa96-bdf7-68d7-a5ec6ed985d7@acm.org> (raw)
In-Reply-To: <20220615054909.GA22044@lst.de>
On 6/14/22 22:49, Christoph Hellwig wrote:
> On Tue, Jun 14, 2022 at 04:56:52PM -0700, Bart Van Assche wrote:
>> The performance penalty of zone locking is not acceptable for our use case.
>> Does this mean that zone locking needs to be preserved for AHCI but not for
>> UFS?
>
> It means you use case needs to use zone append, and we need to make sure
> it is added to SCSI assuming your are on SCSI based on your other comments.
Unfortunately I do not know enough about F2FS to comment on whether or
not making it use REQ_OP_ZONE_APPEND instead of REQ_OP_WRITE is feasible.
Bart.
next prev parent reply other threads:[~2022-06-15 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 17:49 [PATCH 0/5] Improve zoned storage write performance Bart Van Assche
2022-06-14 17:49 ` [PATCH 1/5] block: Introduce the blk_rq_is_seq_write() function Bart Van Assche
2022-06-16 20:41 ` Jens Axboe
2022-06-16 21:16 ` Bart Van Assche
2022-06-14 17:49 ` [PATCH 2/5] scsi: Retry unaligned zoned writes Bart Van Assche
2022-06-14 21:47 ` Khazhy Kumykov
2022-06-14 22:39 ` Bart Van Assche
2022-06-14 23:50 ` Damien Le Moal
2022-06-14 23:54 ` Bart Van Assche
2022-06-15 0:55 ` Damien Le Moal
2022-06-14 23:29 ` Damien Le Moal
2022-06-14 23:56 ` Bart Van Assche
2022-06-15 1:09 ` Damien Le Moal
2022-06-15 5:49 ` Christoph Hellwig
2022-06-15 7:21 ` Damien Le Moal
2022-06-15 19:38 ` Bart Van Assche
2022-06-16 0:14 ` Damien Le Moal
2022-06-15 19:42 ` Bart Van Assche [this message]
2022-06-16 18:36 ` Bart Van Assche
2022-06-14 17:49 ` [PATCH 3/5] nvme: Make the number of retries request specific Bart Van Assche
2022-06-14 17:49 ` [PATCH 4/5] nvme: Increase the number of retries for zoned writes Bart Van Assche
2022-06-14 18:03 ` Keith Busch
2022-06-14 17:49 ` [PATCH 5/5] block/mq-deadline: Remove zone locking Bart Van Assche
2022-06-14 23:40 ` 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=78ba5207-aa96-bdf7-68d7-a5ec6ed985d7@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.