From: Hou Pu <houpu.main@gmail.com>
To: josef@toxicpanda.com, axboe@kernel.dk, mchristi@redhat.com
Cc: linux-block@vger.kernel.org, nbd@other.debian.org,
Hou Pu <houpu@bytedance.com>
Subject: [PATCH 0/2] requeue request if only one connection is configured
Date: Wed, 19 Feb 2020 01:31:05 -0500 [thread overview]
Message-ID: <20200219063107.25550-1-houpu@bytedance.com> (raw)
Hello,
NBD server could be upgraded if we have multiple connections.
But if we have only one connection, after we take down NBD server,
all inflight IO could finally timeout and return error. These
patches fix this using current reconfiguration framework.
I noticed that Mike has following patchset
nbd: local daemon restart support
https://lore.kernel.org/linux-block/5DD41C49.3080209@redhat.com/
It add another netlink interface (NBD_ATTR_SWAP_SOCKETS) and requeue
request immediately after recongirure/swap socket. It do not need to
wait for timeout to fire and requeue in timeout handler, which seems more
like an improvement. Let fix this in current framework first.
Hou Pu (2):
nbd: enable replace socket if only one connection is configured
nbd: requeue command if the soecket is changed
drivers/block/nbd.c | 24 ++++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
--
2.11.0
next reply other threads:[~2020-02-19 6:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 6:31 Hou Pu [this message]
2020-02-19 6:31 ` [PATCH 1/2] nbd: enable replace socket if only one connection is configured Hou Pu
2020-02-25 6:32 ` Mike Christie
2020-02-25 14:10 ` Hou Pu
2020-02-19 6:31 ` [PATCH 2/2] nbd: requeue command if the soecket is changed Hou Pu
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=20200219063107.25550-1-houpu@bytedance.com \
--to=houpu.main@gmail.com \
--cc=axboe@kernel.dk \
--cc=houpu@bytedance.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=nbd@other.debian.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