qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org,
	vsementsov@virtuozzo.com, rjones@redhat.com, stefanha@redhat.com
Subject: [PATCH v3 0/6] Exposing backing-chain allocation over NBD
Date: Thu,  8 Oct 2020 21:07:08 -0500	[thread overview]
Message-ID: <20201009020714.1074061-1-eblake@redhat.com> (raw)

v2 was here:
https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg10926.html

Since then:
rebase to master
patches 1-3/5 of v2 are in pull request
patch 4/5 in v2 (1/6 here) includes improvements from Vladimir
patches 3-6/6 here are new (and I hope to have public patches to
libnbd's 'nbdinfo --map' to take advantage of it posted soon...)

Based-on: <20201008185951.1026052-1-eblake@redhat.com>
([PULL 0/8] NBD patches through 2020-10-08)

Also available at:
https://repo.or.cz/qemu/ericb.git/shortlog/refs/tags/nbd-alloc-depth-v3

001/6:[0056] [FC] 'nbd: Add new qemu:allocation-depth metacontext'
002/6:[0002] [FC] 'nbd: Add 'qemu-nbd -A' to expose allocation depth'
003/6:[down] 'nbd: Update qapi to support multiple bitmaps'
004/6:[down] 'nbd: Simplify qemu bitmap context name'
005/6:[down] 'nbd: Refactor counting of meta contexts'
006/6:[down] 'nbd: Allow export of multiple bitmaps for one device'

Eric Blake (6):
  nbd: Add new qemu:allocation-depth metacontext
  nbd: Add 'qemu-nbd -A' to expose allocation depth
  nbd: Update qapi to support multiple bitmaps
  nbd: Simplify qemu bitmap context name
  nbd: Refactor counting of meta contexts
  nbd: Allow export of multiple bitmaps for one device

 docs/interop/nbd.txt       |  23 +++-
 docs/tools/qemu-nbd.rst    |   6 ++
 qapi/block-core.json       |   7 +-
 qapi/block-export.json     |  20 +++-
 include/block/nbd.h        |   8 +-
 blockdev-nbd.c             |  20 +++-
 nbd/server.c               | 210 +++++++++++++++++++++++++++++--------
 qemu-nbd.c                 |  25 +++--
 tests/qemu-iotests/291     |   6 +-
 tests/qemu-iotests/309     |  73 +++++++++++++
 tests/qemu-iotests/309.out |  22 ++++
 tests/qemu-iotests/group   |   1 +
 12 files changed, 350 insertions(+), 71 deletions(-)
 create mode 100755 tests/qemu-iotests/309
 create mode 100644 tests/qemu-iotests/309.out

-- 
2.28.0



             reply	other threads:[~2020-10-09  2:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  2:07 Eric Blake [this message]
2020-10-09  2:07 ` [PATCH v3 1/6] nbd: Add new qemu:allocation-depth metacontext Eric Blake
2020-10-09  2:07 ` [PATCH v3 2/6] nbd: Add 'qemu-nbd -A' to expose allocation depth Eric Blake
2020-10-09  8:10   ` Markus Armbruster
2020-10-09  9:03     ` Richard W.M. Jones
2020-10-09 12:13       ` Eric Blake
2020-10-09  2:07 ` [PATCH v3 3/6] nbd: Update qapi to support multiple bitmaps Eric Blake
2020-10-09  2:07 ` [PATCH v3 4/6] nbd: Simplify qemu bitmap context name Eric Blake
2020-10-09  2:07 ` [PATCH v3 5/6] nbd: Refactor counting of meta contexts Eric Blake
2020-10-09  2:07 ` [PATCH v3 6/6] nbd: Allow export of multiple bitmaps for one device Eric Blake

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=20201009020714.1074061-1-eblake@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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).