From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Bart Van Assche <bvanassche@acm.org>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Subject: Re: [blktests] zbd/012: Test requeuing of zoned writes and queue freezing
Date: Wed, 27 Nov 2024 20:39:35 -0800 [thread overview]
Message-ID: <Z0f0B6Xf-jdc_fx-@infradead.org> (raw)
In-Reply-To: <16e543dd-c4e6-4f79-b401-8030d7ba1514@kernel.org>
On Thu, Nov 28, 2024 at 01:37:46PM +0900, Damien Le Moal wrote:
> suggested: a BLK_ZONE_WPLUG_NEED_WP_UPDATE flag that is set on error and an
> automatic update of the zone write plug to the start sector of a bio when we
> start seeing writes again for that zone. The idea is that well-behaved users
> will do a report zone after a failed write and restart writing at the correct
> position.
>
> And for good measures, I modified report zones to also automatically update the
> wp of zones that have BLK_ZONE_WPLUG_NEED_WP_UPDATE. So the user doing a report
> zones clears everything up.
>
> Overall, that removes *a lot* of code and makes things a lot simpler. Starting
> test runs with that now.
How does that work for zone append emulation?
next prev parent reply other threads:[~2024-11-28 4:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 21:10 [blktests] zbd/012: Test requeuing of zoned writes and queue freezing Bart Van Assche
2024-11-26 8:34 ` Damien Le Moal
2024-11-26 13:44 ` Bart Van Assche
2024-11-27 5:18 ` Damien Le Moal
2024-11-27 6:16 ` Christoph Hellwig
2024-11-27 6:21 ` Christoph Hellwig
2024-11-27 6:32 ` Damien Le Moal
2024-11-27 6:33 ` Christoph Hellwig
2024-11-27 6:43 ` Damien Le Moal
2024-11-27 6:45 ` Christoph Hellwig
2024-11-27 7:02 ` Damien Le Moal
2024-11-27 7:19 ` Christoph Hellwig
2024-11-27 8:17 ` Damien Le Moal
2024-11-27 8:58 ` Christoph Hellwig
2024-11-27 11:31 ` Damien Le Moal
2024-11-27 16:58 ` Christoph Hellwig
2024-11-27 23:18 ` Damien Le Moal
2024-11-27 23:36 ` Bart Van Assche
2024-11-27 23:43 ` Damien Le Moal
2024-11-28 3:20 ` Christoph Hellwig
2024-11-28 4:37 ` Damien Le Moal
2024-11-28 4:39 ` Christoph Hellwig [this message]
2024-11-28 4:52 ` Damien Le Moal
2024-11-28 5:00 ` Christoph Hellwig
2024-11-28 5:07 ` Damien Le Moal
2024-11-28 5:16 ` Christoph Hellwig
2024-11-28 5:19 ` Damien Le Moal
2024-11-28 5:21 ` Christoph Hellwig
2024-11-28 5:27 ` Damien Le Moal
2024-11-27 17:10 ` Bart Van Assche
2024-11-27 23:11 ` Damien Le Moal
2024-11-26 11:26 ` Damien Le Moal
2024-11-26 12:49 ` Christoph Hellwig
2024-11-27 2:28 ` Damien Le Moal
2024-11-28 4:35 ` Shinichiro Kawasaki
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=Z0f0B6Xf-jdc_fx-@infradead.org \
--to=hch@infradead.org \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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.