From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 5F79DF72 for ; Tue, 22 Dec 2015 09:11:23 +0100 (CET) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 9D711A8B; Tue, 22 Dec 2015 08:11:22 +0000 (UTC) Received: from pxdev.xzpeter.org (vpn1-6-183.pek2.redhat.com [10.72.6.183]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tBM8BATl011759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Dec 2015 03:11:16 -0500 Date: Tue, 22 Dec 2015 16:11:08 +0800 From: Peter Xu To: Yuanhan Liu Message-ID: <20151222081108.GF7532@pxdev.xzpeter.org> References: <1449027793-30975-1-git-send-email-yuanhan.liu@linux.intel.com> <1450321921-27799-1-git-send-email-yuanhan.liu@linux.intel.com> <1450321921-27799-6-git-send-email-yuanhan.liu@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1450321921-27799-6-git-send-email-yuanhan.liu@linux.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 Cc: "Michael S. Tsirkin" , dev@dpdk.org, Victor Kaplansky Subject: Re: [dpdk-dev] [PATCH v2 5/6] vhost: claim that we support GUEST_ANNOUNCE feature X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 08:11:23 -0000 On Thu, Dec 17, 2015 at 11:12:00AM +0800, Yuanhan Liu wrote: > It's actually a feature already enabled in Linux kernel. What we need to > do is simply to claim that we support such feature, and nothing else. > > With that, the guest will send GARP messages after live migration. > > Signed-off-by: Yuanhan Liu > --- > lib/librte_vhost/virtio-net.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/lib/librte_vhost/virtio-net.c b/lib/librte_vhost/virtio-net.c > index 03044f6..0ba5045 100644 > --- a/lib/librte_vhost/virtio-net.c > +++ b/lib/librte_vhost/virtio-net.c > @@ -74,6 +74,7 @@ static struct virtio_net_config_ll *ll_root; > #define VHOST_SUPPORTED_FEATURES ((1ULL << VIRTIO_NET_F_MRG_RXBUF) | \ > (1ULL << VIRTIO_NET_F_CTRL_VQ) | \ > (1ULL << VIRTIO_NET_F_CTRL_RX) | \ > + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \ Do we really need this? I can understand when guest declare with this VIRTIO_NET_F_GUEST_ANNOUNCE flag. With that, guest itself will handle the announcement after migration. However, how could I understand if it's declared by a vhost-user backend? What does it mean? In vhost-user.txt (in QEMU repo docs/specs/), the only place that mentioned this is SEND_RARP: * VHOST_USER_SEND_RARP Id: 19 Equivalent ioctl: N/A Master payload: u64 Ask vhost user backend to broadcast a fake RARP to notify the migration is terminated for guest that does not support GUEST_ANNOUNCE. ... Here, it mention the GUEST_ANNOUNCE since when guest support this, we do not need to send SEND_RARP to vhost-user backend again. It never explain what does it mean when vhost-user declaring to have this flag... Thanks. Peter > (VHOST_SUPPORTS_MQ) | \ > (1ULL << VIRTIO_F_VERSION_1) | \ > (1ULL << VHOST_F_LOG_ALL) | \ > -- > 1.9.0 >