From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Coquelin Subject: Re: [PATCH v3 21/22] vhost: do not destroy device on repeat mem table message Date: Fri, 31 Mar 2017 11:26:22 +0200 Message-ID: References: <1490253059-28112-1-git-send-email-yuanhan.liu@linux.intel.com> <1490705142-893-1-git-send-email-yuanhan.liu@linux.intel.com> <1490705142-893-22-git-send-email-yuanhan.liu@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Harris James R , Liu Changpeng To: Yuanhan Liu , dev@dpdk.org Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 25113FE5 for ; Fri, 31 Mar 2017 11:26:26 +0200 (CEST) In-Reply-To: <1490705142-893-22-git-send-email-yuanhan.liu@linux.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 03/28/2017 02:45 PM, Yuanhan Liu wrote: > It doesn't make any sense to invoke destroy_device() callback at > while handling SET_MEM_TABLE message. > > From the vhost-user spec, it's the GET_VRING_BASE message indicates > the end of a vhost device: the destroy_device() should be invoked > from there (luckily, we already did that). > > Signed-off-by: Yuanhan Liu > --- > lib/librte_vhost/vhost_user.c | 6 ------ > 1 file changed, 6 deletions(-) Reviewed-by: Maxime Coquelin Thanks, Maxime