All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Josef Bacik <josef@toxicpanda.com>,
	nbd-general@lists.sourceforge.net, linux-block@vger.kernel.org,
	kernel-team@fb.com
Subject: Re: [PATCH 00/12] nbd: Netlink interface and path failure enhancements
Date: Mon, 17 Apr 2017 09:59:27 -0600	[thread overview]
Message-ID: <d58e5d19-9bda-e5a0-55a1-00aee6ecb3b3@kernel.dk> (raw)
In-Reply-To: <1491512527-4286-1-git-send-email-jbacik@fb.com>

On 04/06/2017 03:01 PM, Josef Bacik wrote:
> This patchset adds a new netlink configuration interface to NBD as well as a
> bunch of enhancments around path failures.  The patches provide the following
> enhancemnts to NBD
> 
>  - Netlink configuration interface that doesn't leave a userspace application
>    waiting in kernel space for the device to disconnect.
>  - Netlink reconfigure interface for adding re-connected sockets to replace dead
>    sockets.
>  - A flag to destroy the NBD device on disconnect, much like how mount -o loop
>    works.
>  - A status interface that currently will only report whether a device is
>    connected or not, but can be extended to include whatever in the future.
>  - A netlink multicast notification scheme to notify user space when there are
>    connection issues to allow for seamless reconnects.
>  - Dead link handling.  You can specify a dead link timeout and the NBD device
>    will pause IO for that timeout waiting to see if the connection can be
>    re-established.  This is helpful to allow for things like nbd server upgrades
>    where the whole server disappears for a short period of time.
> 
> These patches have been thorougly and continuously tested for about a month.
> I've been finding bugs in various places, but this batch has been solid for the
> last few days of testing, which include a constant disconnect/reconnect torture
> test.  Thanks,

Added for 4.12, thanks.

-- 
Jens Axboe

      parent reply	other threads:[~2017-04-17 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 21:01 [PATCH 00/12] nbd: Netlink interface and path failure enhancements Josef Bacik
2017-04-06 21:01 ` [PATCH 01/12] nbd: put socket in error cases Josef Bacik
2017-04-06 21:01 ` [PATCH 02/12] nbd: handle single path failures gracefully Josef Bacik
2017-04-06 21:01 ` [PATCH 03/12] nbd: separate out the config information Josef Bacik
2017-04-06 21:01 ` [PATCH 04/12] nbd: stop using the bdev everywhere Josef Bacik
2017-04-06 21:02 ` [PATCH 05/12] nbd: add a basic netlink interface Josef Bacik
2017-04-06 21:02 ` [PATCH 06/12] nbd: add a reconfigure netlink command Josef Bacik
2017-04-06 21:02 ` [PATCH 07/12] nbd: multicast dead link notifications Josef Bacik
2017-04-06 21:02 ` [PATCH 08/12] nbd: only clear the queue on device teardown Josef Bacik
2017-04-06 21:02 ` [PATCH 09/12] nbd: handle dead connections Josef Bacik
2017-04-06 21:02 ` [PATCH 10/12] nbd: add a status netlink command Josef Bacik
2017-04-06 21:02 ` [PATCH 11/12] nbd: add device refcounting Josef Bacik
2017-04-06 21:02 ` [PATCH 12/12] nbd: add a flag to destroy an nbd device on disconnect Josef Bacik
2017-04-06 21:05 ` [PATCH 00/12] nbd: Netlink interface and path failure enhancements Josef Bacik
2017-04-07 13:04   ` [Nbd] " Wouter Verhelst
2017-04-17 15:59 ` Jens Axboe [this message]

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=d58e5d19-9bda-e5a0-55a1-00aee6ecb3b3@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=nbd-general@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.