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 0/4] nbd: reduce max_block restrictions
Date: Thu, 11 Jun 2020 19:26:51 +0300 [thread overview]
Message-ID: <20200611162655.4538-1-vsementsov@virtuozzo.com> (raw)
Recent changes in NBD protocol allowed to use some commands without
max_block restriction. Let's drop the restrictions.
NBD change is here:
https://github.com/NetworkBlockDevice/nbd/commit/9f30fedb8699f151e7ef4ccc07e624330be3316b#diff-762fb7c670348da69cc9050ef58fe3ae
v4: fix auto_no_fallback variable usage in 04:
- initialize it
- unset it on error
Hope, it will fix bug reported by patchew
Vladimir Sementsov-Ogievskiy (4):
block: add max_pwrite_zeroes_fast to BlockLimits
block/nbd: define new max_write_zero_fast limit
block/io: refactor bdrv_co_do_pwrite_zeroes head calculation
block/io: auto-no-fallback for write-zeroes
include/block/block_int.h | 8 ++++++++
block/io.c | 40 +++++++++++++++++++++++++++++++++------
block/nbd.c | 1 +
3 files changed, 43 insertions(+), 6 deletions(-)
--
2.21.0
next reply other threads:[~2020-06-11 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:26 Vladimir Sementsov-Ogievskiy [this message]
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 ` [PATCH v4 4/4] block/io: auto-no-fallback for write-zeroes Vladimir Sementsov-Ogievskiy
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-1-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).