From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, vsementsov@virtuozzo.com,
sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
mreitz@redhat.com, stefanha@redhat.com, den@openvz.org,
namei.unix@gmail.com
Subject: [Qemu-devel] [PATCH v8 0/3] NBD reconnect
Date: Wed, 21 Aug 2019 19:52:12 +0300 [thread overview]
Message-ID: <20190821165215.61406-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here is NBD reconnect. Previously, if connection failed all current
and future requests will fail. After the series, nbd-client driver
will try to reconnect unlimited times. During first @reconnect-delay
seconds of reconnecting all requests will wait for the connection,
and if it is established requests will be resent. After
@reconnect-delay period all requests will be failed (until successful
reconnect).
v8:
preparations are already merged [thx to Eric], old 07 with SI_* constants
dropped [Peter]
02: - use NANOSECONDS_PER_SECOND
03: - move to tests/qemu-iotests/264
- limit job speed, otherwise it fails on ramfs as backup finishes too early
v7:
almost all: rebased on merged nbd.c and nbd-client.c (including patch subject)
01-04: add Eric's r-b
04: wording
05: new
06: rewrite to remove timer earlier
07: new
08:
- rebase on 05 and 07
- drop "All rights reserved"
- handle drain
- improve handling aio context attach
09: move 249 -> 257
Vladimir Sementsov-Ogievskiy (3):
qemu-coroutine-sleep: introduce qemu_co_sleep_wake
block/nbd: nbd reconnect
iotests: test nbd reconnect
include/qemu/coroutine.h | 17 +-
block/nbd.c | 335 +++++++++++++++++++++++++++-------
block/null.c | 2 +-
block/sheepdog.c | 2 +-
tests/test-bdrv-drain.c | 6 +-
tests/test-block-iothread.c | 2 +-
util/qemu-coroutine-sleep.c | 47 +++--
tests/qemu-iotests/264 | 65 +++++++
tests/qemu-iotests/264.out | 12 ++
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/iotests.py | 4 +
11 files changed, 408 insertions(+), 85 deletions(-)
create mode 100755 tests/qemu-iotests/264
create mode 100644 tests/qemu-iotests/264.out
--
2.18.0
next reply other threads:[~2019-08-21 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 16:52 Vladimir Sementsov-Ogievskiy [this message]
2019-08-21 16:52 ` [Qemu-devel] [PATCH v8 1/3] qemu-coroutine-sleep: introduce qemu_co_sleep_wake Vladimir Sementsov-Ogievskiy
2019-08-21 17:15 ` Eric Blake
2019-09-17 15:27 ` Kevin Wolf
2019-09-17 15:50 ` Vladimir Sementsov-Ogievskiy
2019-08-21 16:52 ` [Qemu-devel] [PATCH v8 2/3] block/nbd: nbd reconnect Vladimir Sementsov-Ogievskiy
2019-08-21 17:35 ` Eric Blake
2019-08-22 11:58 ` Vladimir Sementsov-Ogievskiy
2019-08-21 16:52 ` [Qemu-devel] [PATCH v8 3/3] iotests: test " Vladimir Sementsov-Ogievskiy
2019-09-05 8:59 ` [Qemu-devel] [PATCH v8 0/3] NBD reconnect Vladimir Sementsov-Ogievskiy
2019-09-17 8:16 ` [Qemu-devel] ping " 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=20190821165215.61406-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=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.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).