From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL v2 0/9] NBD patches through 2019-09-05
Date: Thu, 5 Sep 2019 16:15:13 -0500 [thread overview]
Message-ID: <20190905211522.2824-1-eblake@redhat.com> (raw)
The following changes since commit eac2f39602e0423adf56be410c9a22c31fec9a81:
target/arm: Inline gen_bx_im into callers (2019-09-05 13:23:04 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pull-nbd-2019-09-05-v2
for you to fetch changes up to b491dbb7f8e09ef864770c205a3b5bce6c5c1881:
nbd: Implement server use of NBD FAST_ZERO (2019-09-05 16:04:53 -0500)
v2 pull request: fix iotests 223 and 233 (only re-sending the patches
that needed tweaking, per this backport-diff):
001/9:[0002] [FC] 'nbd: Advertise multi-conn for shared read-only connections'
002/9:[----] [--] 'nbd: Use g_autofree in a few places'
003/9:[0008] [FC] 'nbd: Tolerate more errors to structured reply request'
004/9:[----] [--] 'block: workaround for unaligned byte range in fallocate()'
005/9:[----] [--] 'docs: Update preferred NBD device syntax'
006/9:[0002] [FC] 'nbd: Improve per-export flag handling in server'
007/9:[----] [--] 'nbd: Prepare for NBD_CMD_FLAG_FAST_ZERO'
008/9:[----] [--] 'nbd: Implement client use of NBD FAST_ZERO'
009/9:[0004] [FC] 'nbd: Implement server use of NBD FAST_ZERO'
----------------------------------------------------------------
nbd patches for 2019-09-05
- Advertise NBD_FLAG_CAN_MULTI_CONN on readonly images
- Tolerate larger set of server error responses during handshake
- More precision on handling fallocate() failures due to alignment
- Better documentation of NBD connection URIs
- Implement new extension NBD_CMD_FLAG_FAST_ZERO to benefit qemu-img convert
----------------------------------------------------------------
Andrey Shinkevich (1):
block: workaround for unaligned byte range in fallocate()
Eric Blake (8):
nbd: Advertise multi-conn for shared read-only connections
nbd: Use g_autofree in a few places
nbd: Tolerate more errors to structured reply request
docs: Update preferred NBD device syntax
nbd: Improve per-export flag handling in server
nbd: Prepare for NBD_CMD_FLAG_FAST_ZERO
nbd: Implement client use of NBD FAST_ZERO
nbd: Implement server use of NBD FAST_ZERO
docs/interop/nbd.txt | 2 ++
qemu-doc.texi | 11 ++++--
include/block/nbd.h | 6 +++-
block/io.c | 2 +-
block/file-posix.c | 7 ++++
block/nbd.c | 18 ++++++----
blockdev-nbd.c | 3 +-
nbd/client.c | 85 ++++++++++++++++++++++------------------------
nbd/common.c | 5 +++
nbd/server.c | 83 +++++++++++++++++++++++++-------------------
qemu-nbd.c | 7 ++--
nbd/trace-events | 2 +-
tests/qemu-iotests/223.out | 4 +--
tests/qemu-iotests/233.out | 10 +++---
14 files changed, 141 insertions(+), 104 deletions(-)
--
2.21.0
next reply other threads:[~2019-09-05 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 21:15 Eric Blake [this message]
2019-09-05 21:15 ` [Qemu-devel] [PULL v2 1/9] nbd: Advertise multi-conn for shared read-only connections Eric Blake
2019-09-05 21:15 ` [Qemu-devel] [PULL v2 3/9] nbd: Tolerate more errors to structured reply request Eric Blake
2019-09-05 21:15 ` [Qemu-devel] [PULL v2 6/9] nbd: Improve per-export flag handling in server Eric Blake
2019-09-05 21:15 ` [Qemu-devel] [PULL v2 9/9] nbd: Implement server use of NBD FAST_ZERO Eric Blake
2019-09-09 8:48 ` [Qemu-devel] [PULL v2 0/9] NBD patches through 2019-09-05 Peter Maydell
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=20190905211522.2824-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).