From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 4E5B52BE3 for ; Thu, 21 Apr 2016 18:52:37 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga104.fm.intel.com with ESMTP; 21 Apr 2016 09:52:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,513,1455004800"; d="scan'208";a="937380004" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by orsmga001.jf.intel.com with ESMTP; 21 Apr 2016 09:52:34 -0700 Date: Thu, 21 Apr 2016 09:54:03 -0700 From: Yuanhan Liu To: Ilya Maximets Cc: dev@dpdk.org, christian.ehrhardt@canonical.com, Daniele Di Proietto , "dev@openvswitch.org" , Dyasly Sergey Message-ID: <20160421165403.GA11584@yliu-dev.sh.intel.com> References: <5718B306.5070801@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5718B306.5070801@samsung.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] Memory leak when adding/removing vhost_user ports 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: Thu, 21 Apr 2016 16:52:37 -0000 On Thu, Apr 21, 2016 at 02:01:26PM +0300, Ilya Maximets wrote: > Hi, Christian. > You're, likely, using tar archive with openvswitch from openvswitch.org. > It doesn't contain many bug fixes from git/branch-2.5 unfortunately. > > The problem that you are facing has been solved in branch-2.5 by > > commit d9df7b9206831631ddbd90f9cbeef1b4fc5a8e89 > Author: Ilya Maximets > Date: Thu Mar 3 11:30:06 2016 +0300 > > netdev-dpdk: Fix memory leak in netdev_dpdk_vhost_destruct(). > > Fixes: 4573fbd38fa1 ("netdev-dpdk: Add vhost-user multiqueue support") > Signed-off-by: Ilya Maximets > Acked-by: Flavio Leitner > Acked-by: Daniele Di Proietto Hi Ilya, Thanks for the info. And, I actually checked this peice of code. I was using new code, so, I didn't find anything wrong. --yliu