From: Alexey Dobriyan <adobriyan@gmail.com>
To: axboe@kernel.dk
Cc: fio@vger.kernel.org, damien.lemoal@wdc.com
Subject: Re: [PATCH 8/9] zbd: support verification
Date: Tue, 5 May 2020 20:59:29 +0300 [thread overview]
Message-ID: <20200505175929.GA2719@avx2> (raw)
In-Reply-To: <20200505175634.2517-8-adobriyan@gmail.com>
On Tue, May 05, 2020 at 08:56:34PM +0300, Alexey Dobriyan wrote:
> Verification is not supported in ZBD mode which is codified in this
> assert:
>
> if (zb->reset_zone || zbd_zone_full(f, zb, min_bs)) {
> assert(td->o.verify == VERIFY_NONE);
This is RFC for now, not for merging, there rest are.
And no, patches haven't been lost, 9/9 is debugging is usual...
next prev parent reply other threads:[~2020-05-05 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 17:56 [PATCH 1/9] verify: decouple seed generation from buffer fill Alexey Dobriyan
2020-05-05 17:56 ` [PATCH 2/9] zbd: bump ZBD_MAX_OPEN_ZONES Alexey Dobriyan
2020-05-05 17:56 ` [PATCH 3/9] zbd: don't lock zones outside working area Alexey Dobriyan
2020-05-05 17:56 ` [PATCH 4/9] zbd: introduce per job maximum open zones limit Alexey Dobriyan
2020-05-11 1:09 ` Damien Le Moal
2020-05-05 17:56 ` [PATCH 5/9] zbd: make zbd_info->mutex non-recursive Alexey Dobriyan
2020-05-11 1:11 ` Damien Le Moal
2020-05-05 17:56 ` [PATCH 6/9] zbd: consolidate zone mutex initialisation Alexey Dobriyan
2020-05-11 1:16 ` Damien Le Moal
2020-05-21 21:44 ` Alexey Dobriyan
2020-05-21 22:02 ` Damien Le Moal
2020-05-21 22:27 ` Alexey Dobriyan
2020-05-05 17:56 ` [PATCH 7/9] fio: parse "io_size=1%" Alexey Dobriyan
2020-05-11 1:20 ` Damien Le Moal
2020-05-21 22:13 ` Alexey Dobriyan
2020-05-05 17:56 ` [PATCH 8/9] zbd: support verification Alexey Dobriyan
2020-05-05 17:59 ` Alexey Dobriyan [this message]
2020-05-11 2:01 ` Damien Le Moal
2020-05-11 1:59 ` Damien Le Moal
2020-05-11 16:00 ` Alexey Dobriyan
2020-05-11 0:56 ` [PATCH 1/9] verify: decouple seed generation from buffer fill 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=20200505175929.GA2719@avx2 \
--to=adobriyan@gmail.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=fio@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