From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH v3] rte_vhost: added user callbacks for socket open/close Date: Tue, 10 Oct 2017 11:14:14 +0800 Message-ID: <20171010031414.GQ1545@yliu-home> References: <1503419092-63814-1-git-send-email-dariuszx.stojaczyk@intel.com> <1504090258-164350-1-git-send-email-dariuszx.stojaczyk@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, Pawel Wodkowski , jfreimann@redhat.com, maxime.coquelin@redhat.com To: Dariusz Stojaczyk Return-path: Received: from new2-smtp.messagingengine.com (new2-smtp.messagingengine.com [66.111.4.224]) by dpdk.org (Postfix) with ESMTP id 6D2F91B246 for ; Tue, 10 Oct 2017 05:14:19 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1504090258-164350-1-git-send-email-dariuszx.stojaczyk@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Aug 30, 2017 at 12:50:58PM +0200, Dariusz Stojaczyk wrote: > Added new callbacks to notify about socket connection status. > As destroy_device is used for virtqueue processing *pause* as well as > connection close, the user has no distinction between those. > > Consider the following scenario: > rte_vhost: received SET_VRING_BASE message, > calling destroy_device() as usual > > user: end-user asks to remove the device (together with socket file), > OK, device is not *in use* - that's NOT the behavior we want > calling rte_vhost_driver_unregister() etc. > > Instead of changing new_device/destroy_device callbacks and breaking > the ABI, a set of new functions new_connection/destroy_connection > has been added. > > Signed-off-by: Dariusz Stojaczyk > --- > v3: improved err-handling path and updated commit msg > v2: also updated vhost_lib.rst The doc update is missing. I have cherry-picked it from v2. Applied to dpdk-next-virtio. Thanks. --yliu