All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
	Tetsuya Mukawa <mukawa@igel.co.jp>,
	jonshin@cisco.com, Ilya Maximets <i.maximets@samsung.com>,
	"Xie, Huawei" <huawei.xie@intel.com>
Subject: Re: [Qemu-devel] [PATCH 00/10] RFCv3: vhost-user: simple reconnection support
Date: Tue, 10 May 2016 10:14:01 -0700	[thread overview]
Message-ID: <20160510171401.GP5641@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1462896240-30999-1-git-send-email-marcandre.lureau@redhat.com>

Hi Marc,

I was also thinking we should do it in this way first. That simplfies
things. So, feel free to add:

Tested-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Reviewed-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>

(well, I didn't review the test case carefully).

Thanks.

	--yliu

On Tue, May 10, 2016 at 06:03:50PM +0200, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
> 
> Hi,
> 
> In a previous series "RFCv2: vhost-user: shutdown and reconnection", I
> proposed to add a new slave request to handle graceful shutdown, for
> both qemu configuration, server or client, while keeping the guest
> running with link down status.
> 
> However, for the simple case where qemu is configured as server, and
> the backend processes packets in order and disconnects, it is possible
> for the backend to recover after reconnection by discarding the qemu
> SET_VRING_BASE value and resuming from the used->index instead. This
> simplifies the reconnection support in this particular situation (it
> would make sense to have the backend declare this behaviour with an
> extra flag)
> 
> The guest won't be notified of link status change and queues may not
> be processed in a timely manner, also qemu may assert if some
> vhost-user commands are happening while the backend is disconnected.
> So the reconnection must happen "quickly enough" here. In order to
> keep the series relatively small, these further problems will be
> addressed later.
> 
> These series demonstrates a simple reconnect support for vubr
> (configured as client and qemu as server), includes some nice to
> have fixes and a simple test.
> 
> Marc-André Lureau (8):
>   vubr: add client mode
>   vubr: workaround stale vring base
>   vhost-user: disconnect on start failure
>   vhost-net: do not crash if backend is not present
>   vhost-net: save & restore vhost-user acked features
>   vhost-net: save & restore vring enable state
>   tests: append i386 tests
>   test: start vhost-user reconnect test
> 
> Tetsuya Mukawa (2):
>   vhost-user: add ability to know vhost-user backend disconnection
>   qemu-char: add qemu_chr_disconnect to close a fd accepted by listen fd
> 
>  hw/net/vhost_net.c        |  39 ++++++++++++++-
>  include/net/net.h         |   1 +
>  include/net/vhost-user.h  |   1 +
>  include/net/vhost_net.h   |   3 ++
>  include/sysemu/char.h     |   7 +++
>  net/vhost-user.c          |  32 +++++++++++-
>  qemu-char.c               |   8 +++
>  tests/Makefile            |   2 +-
>  tests/vhost-user-bridge.c |  45 ++++++++++++-----
>  tests/vhost-user-test.c   | 123 +++++++++++++++++++++++++++++++++++++++-------
>  10 files changed, 228 insertions(+), 33 deletions(-)
> 
> -- 
> 2.7.4

      parent reply	other threads:[~2016-05-10 17:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-10 16:03 [Qemu-devel] [PATCH 00/10] RFCv3: vhost-user: simple reconnection support marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 01/10] vhost-user: add ability to know vhost-user backend disconnection marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 02/10] vubr: add client mode marcandre.lureau
2016-05-10 17:19   ` Yuanhan Liu
2016-05-10 18:08     ` Marc-André Lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 03/10] vubr: workaround stale vring base marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 04/10] qemu-char: add qemu_chr_disconnect to close a fd accepted by listen fd marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 05/10] vhost-user: disconnect on start failure marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 06/10] vhost-net: do not crash if backend is not present marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 07/10] vhost-net: save & restore vhost-user acked features marcandre.lureau
2016-06-06  9:06   ` Yuanhan Liu
2016-06-06  9:50     ` Marc-André Lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 08/10] vhost-net: save & restore vring enable state marcandre.lureau
2016-05-10 16:03 ` [Qemu-devel] [PATCH 09/10] tests: append i386 tests marcandre.lureau
2016-05-10 16:04 ` [Qemu-devel] [PATCH 10/10] test: start vhost-user reconnect test marcandre.lureau
2016-05-10 16:19 ` [Qemu-devel] [PATCH 00/10] RFCv3: vhost-user: simple reconnection support Michael S. Tsirkin
2016-05-10 16:28   ` Marc-André Lureau
2016-05-13 18:30     ` Marc-André Lureau
2016-05-15  9:42       ` Michael S. Tsirkin
2016-05-23 13:40         ` Yuanhan Liu
2016-05-24 13:24           ` Marc-André Lureau
2016-05-10 17:14 ` Yuanhan Liu [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=20160510171401.GP5641@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=huawei.xie@intel.com \
    --cc=i.maximets@samsung.com \
    --cc=jonshin@cisco.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=mukawa@igel.co.jp \
    --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 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.