From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, fam@euphon.net, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
den@openvz.org
Subject: [PATCH v4 4/4] block/io: auto-no-fallback for write-zeroes
Date: Thu, 11 Jun 2020 19:26:55 +0300 [thread overview]
Message-ID: <20200611162655.4538-5-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20200611162655.4538-1-vsementsov@virtuozzo.com>
When BDRV_REQ_NO_FALLBACK is supported, the NBD driver supports a
larger request size. Add code to try large zero requests with a
NO_FALLBACK request prior to having to split a request into chunks
according to max_pwrite_zeroes.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
block/io.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/block/io.c b/block/io.c
index 3fae97da2d..ad219cb220 100644
--- a/block/io.c
+++ b/block/io.c
@@ -1778,6 +1778,7 @@ static int coroutine_fn bdrv_co_do_pwrite_zeroes(BlockDriverState *bs,
int alignment = MAX(bs->bl.pwrite_zeroes_alignment,
bs->bl.request_alignment);
int max_transfer = MIN_NON_ZERO(bs->bl.max_transfer, MAX_BOUNCE_BUFFER);
+ bool auto_no_fallback = false;
assert(alignment % bs->bl.request_alignment == 0);
@@ -1785,6 +1786,16 @@ static int coroutine_fn bdrv_co_do_pwrite_zeroes(BlockDriverState *bs,
return -ENOMEDIUM;
}
+ if (!(flags & BDRV_REQ_NO_FALLBACK) &&
+ (bs->supported_zero_flags & BDRV_REQ_NO_FALLBACK) &&
+ bs->bl.max_pwrite_zeroes && bs->bl.max_pwrite_zeroes < bytes &&
+ bs->bl.max_pwrite_zeroes < bs->bl.max_pwrite_zeroes_fast)
+ {
+ assert(drv->bdrv_co_pwrite_zeroes);
+ flags |= BDRV_REQ_NO_FALLBACK;
+ auto_no_fallback = true;
+ }
+
if ((flags & ~bs->supported_zero_flags) & BDRV_REQ_NO_FALLBACK) {
return -ENOTSUP;
}
@@ -1829,6 +1840,14 @@ static int coroutine_fn bdrv_co_do_pwrite_zeroes(BlockDriverState *bs,
if (drv->bdrv_co_pwrite_zeroes) {
ret = drv->bdrv_co_pwrite_zeroes(bs, offset, num,
flags & bs->supported_zero_flags);
+ if (ret == -ENOTSUP && auto_no_fallback) {
+ auto_no_fallback = false;
+ flags &= ~BDRV_REQ_NO_FALLBACK;
+ max_write_zeroes =
+ QEMU_ALIGN_DOWN(MIN_NON_ZERO(bs->bl.max_pwrite_zeroes,
+ INT_MAX), alignment);
+ continue;
+ }
if (ret != -ENOTSUP && (flags & BDRV_REQ_FUA) &&
!(bs->supported_zero_flags & BDRV_REQ_FUA)) {
need_flush = true;
--
2.21.0
prev parent reply other threads:[~2020-06-11 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:26 [PATCH v4 0/4] nbd: reduce max_block restrictions Vladimir Sementsov-Ogievskiy
2020-06-11 16:26 ` [PATCH v4 1/4] block: add max_pwrite_zeroes_fast to BlockLimits Vladimir Sementsov-Ogievskiy
2020-07-23 20:31 ` Eric Blake
2020-06-11 16:26 ` [PATCH v4 2/4] block/nbd: define new max_write_zero_fast limit Vladimir Sementsov-Ogievskiy
2020-07-23 20:32 ` Eric Blake
2020-09-10 11:12 ` Vladimir Sementsov-Ogievskiy
2020-06-11 16:26 ` [PATCH v4 3/4] block/io: refactor bdrv_co_do_pwrite_zeroes head calculation Vladimir Sementsov-Ogievskiy
2020-06-11 16:26 ` Vladimir Sementsov-Ogievskiy [this message]
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=20200611162655.4538-5-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).