From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
vsementsov@virtuozzo.com, eblake@redhat.com
Subject: [PATCH v5 0/5] block/nbd: drop connection_co
Date: Wed, 14 Jul 2021 19:59:11 +0300 [thread overview]
Message-ID: <20210714165916.102363-1-vsementsov@virtuozzo.com> (raw)
Hi all!
That's finally a new version of
[PATCH v3 33/33] block/nbd: drop connection_co
(v4 was sent and merged without that last patch of v3)
I tried to do some things in separate patches, but still
"block/nbd: drop connection_co" is big and complicated.
Vladimir Sementsov-Ogievskiy (5):
block/nbd: nbd_channel_error() shutdown channel unconditionally
block/nbd: move nbd_recv_coroutines_wake_all() up
block/nbd: refactor nbd_recv_coroutines_wake_all()
block/nbd: drop connection_co
block/nbd: check that received handle is valid
block/nbd.c | 412 +++++++++++++++------------------------------------
nbd/client.c | 2 -
2 files changed, 121 insertions(+), 293 deletions(-)
--
2.29.2
next reply other threads:[~2021-07-14 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 16:59 Vladimir Sementsov-Ogievskiy [this message]
2021-07-14 16:59 ` [PATCH v5 1/5] block/nbd: nbd_channel_error() shutdown channel unconditionally Vladimir Sementsov-Ogievskiy
2021-07-16 20:34 ` Eric Blake
2021-07-14 16:59 ` [PATCH v5 2/5] block/nbd: move nbd_recv_coroutines_wake_all() up Vladimir Sementsov-Ogievskiy
2021-07-16 20:35 ` Eric Blake
2021-07-14 16:59 ` [PATCH v5 3/5] block/nbd: refactor nbd_recv_coroutines_wake_all() Vladimir Sementsov-Ogievskiy
2021-07-16 21:25 ` Eric Blake
2021-07-19 9:13 ` Vladimir Sementsov-Ogievskiy
2021-07-14 16:59 ` [PATCH v5 4/5] block/nbd: drop connection_co Vladimir Sementsov-Ogievskiy
2021-07-14 17:07 ` Vladimir Sementsov-Ogievskiy
2021-07-14 16:59 ` [PATCH v5 5/5] block/nbd: check that received handle is valid 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=20210714165916.102363-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).