From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 5A5FEF91E for ; Thu, 12 Jan 2017 05:01:33 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 11 Jan 2017 20:01:32 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,348,1477983600"; d="scan'208";a="807877184" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by FMSMGA003.fm.intel.com with ESMTP; 11 Jan 2017 20:01:31 -0800 Date: Thu, 12 Jan 2017 12:03:44 +0800 From: Yuanhan Liu To: Maxime Coquelin Cc: dev@dpdk.org Message-ID: <20170112040344.GC9770@yliu-dev.sh.intel.com> References: <20161212175400.7978-1-maxime.coquelin@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161212175400.7978-1-maxime.coquelin@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH] vhost: Introduce vhost-user's REPLY_ACK feature X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2017 04:01:33 -0000 On Mon, Dec 12, 2016 at 06:54:00PM +0100, Maxime Coquelin wrote: > REPLY_ACK features provide a generic way for QEMU to ensure both > completion and success of a request. > > As described in vhost-user spec in QEMU repository, QEMU sets > VHOST_USER_NEED_REPLY flag (bit 3) when expecting a reply_ack from > the backend. Backend must reply with 0 for success or non-zero > otherwise when flag is set. > > Currently, only VHOST_USER_SET_MEM_TABLE request implements reply_ack, > in order to synchronize mapping updates. > > This patch enables REPLY_ACK feature generally, but only checks error > code for VHOST_USER_SET_MEM_TABLE. > > Signed-off-by: Maxime Coquelin Applied to dpdk-next-virtio. Thanks. --yliu