From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50594)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <yuanhan.liu@linux.intel.com>) id 1ayAA5-0005ka-6t
	for qemu-devel@nongnu.org; Wed, 04 May 2016 23:41:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <yuanhan.liu@linux.intel.com>) id 1ayA9t-0003bs-Ld
	for qemu-devel@nongnu.org; Wed, 04 May 2016 23:41:07 -0400
Received: from mga04.intel.com ([192.55.52.120]:18735)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <yuanhan.liu@linux.intel.com>) id 1ayA9t-0003Yv-E0
	for qemu-devel@nongnu.org; Wed, 04 May 2016 23:41:01 -0400
Date: Wed, 4 May 2016 20:44:37 -0700
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Message-ID: <20160505034437.GX5641@yliu-dev.sh.intel.com>
References: <20160428052304.GF25677@yliu-dev.sh.intel.com>
	<CAJ+F1CLWsQFOf2kn0bQLmT7HyF=jSDKAf8B+f8zVy-20rZbuxA@mail.gmail.com>
	<20160429174835.GH5641@yliu-dev.sh.intel.com>
	<20160501134233-mutt-send-email-mst@redhat.com>
	<20160501210442.GK5641@yliu-dev.sh.intel.com>
	<20160502080610-mutt-send-email-mst@redhat.com>
	<CAJ+F1CL3nS88PT36AAFJUyQb0=Rigm5gSrc7uOZL5c-9EJ3_sQ@mail.gmail.com>
	<20160502143051-mutt-send-email-mst@redhat.com>
	<CAJ+F1CK0ib34Swuudj=QE8aePn=_usMMFV+8SGrKFouMEhu3mQ@mail.gmail.com>
	<20160504220549-mutt-send-email-mst@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160504220549-mutt-send-email-mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 11/18] vhost-user: add shutdown support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: =?iso-8859-1?Q?Marc-Andr=E9?= Lureau <marcandre.lureau@gmail.com>, QEMU <qemu-devel@nongnu.org>, Ilya Maximets <i.maximets@samsung.com>, jonshin@cisco.com, Tetsuya Mukawa <mukawa@igel.co.jp>, "Xie, Huawei" <huawei.xie@intel.com>

Hello,

On Wed, May 04, 2016 at 10:13:49PM +0300, Michael S. Tsirkin wrote:
> How do you avoid it?
> 
> > > Management is required to make this robust, auto-reconnect
> > > is handy for people bypassing management.
> > 
> > tbh, I don't like autoreconnect. My previous series didn't include
> > this and assumed the feature would be supported only when qemu is
> > configured to be the server. I added reconnect upon request by users.
> 
> I don't have better solutions so OK I guess.

Yes, it's a request from me :)
Well, there may be few others also requested that.

The reason I had this asking is that, so far, we just have only one
vhost-user frontend, and that is QEMU. But we may have many backends,
I'm aware of 4 at the time writing, including the vubr from QEMU.
While we could do vhost-user client and reconnect implementation
on all backends, it's clear that implementing it in the only backend
(QEMU) introduces more benefits.

OTOH, I could implement DPDK vhost-user as client and try reconnect
there, if that could makes all stuff a bit easier.

	--yliu