From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: v.sementsov-og@mail.ru, kwolf@redhat.com, qemu-block@nongnu.org
Subject: [PATCH v4 0/2] nbd: MULTI_CONN for shared writable exports
Date: Wed, 11 May 2022 19:49:22 -0500 [thread overview]
Message-ID: <20220512004924.417153-1-eblake@redhat.com> (raw)
v3 was here:
https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg03701.html
with additional review here:
https://lists.gnu.org/archive/html/qemu-devel/2022-05/msg00166.html
Since then:
- patch 1 of v3 applied independently
- patch 3 simplified with beefed up commit message (now unconditional,
because we have convinced ourselves that all shared clients go
through a single block backend with no cache inconsistency) [kwolf]
- patch 3 rebase iotest addition to recent iotest improvements
- patch 3 s/7.0/7.1/ to match another slip in time
Eric Blake (2):
qemu-nbd: Pass max connections to blockdev layer
nbd/server: Allow MULTI_CONN for shared writable exports
docs/interop/nbd.txt | 1 +
docs/tools/qemu-nbd.rst | 3 +-
qapi/block-export.json | 8 +-
include/block/nbd.h | 5 +-
blockdev-nbd.c | 13 +-
nbd/server.c | 10 +-
qemu-nbd.c | 2 +-
MAINTAINERS | 1 +
tests/qemu-iotests/tests/nbd-multiconn | 145 ++++++++++++++++++
tests/qemu-iotests/tests/nbd-multiconn.out | 5 +
.../tests/nbd-qemu-allocation.out | 2 +-
11 files changed, 178 insertions(+), 17 deletions(-)
create mode 100755 tests/qemu-iotests/tests/nbd-multiconn
create mode 100644 tests/qemu-iotests/tests/nbd-multiconn.out
--
2.36.1
next reply other threads:[~2022-05-12 0:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 0:49 Eric Blake [this message]
2022-05-12 0:49 ` [PATCH v4 1/2] qemu-nbd: Pass max connections to blockdev layer Eric Blake
2022-05-12 0:49 ` [PATCH v4 2/2] nbd/server: Allow MULTI_CONN for shared writable exports Eric Blake
2022-05-12 11:18 ` [PATCH v4 0/2] nbd: " Kevin Wolf
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=20220512004924.417153-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.sementsov-og@mail.ru \
/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).