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 60032C1C0 for ; Thu, 18 Feb 2016 05:08:50 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP; 17 Feb 2016 20:08:49 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,463,1449561600"; d="scan'208";a="748434124" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.66.49]) by orsmga003.jf.intel.com with ESMTP; 17 Feb 2016 20:08:48 -0800 Date: Thu, 18 Feb 2016 12:09:13 +0800 From: Yuanhan Liu To: Thomas Monjalon Message-ID: <20160218040913.GM21426@yliu-dev.sh.intel.com> References: <1449122773-25510-1-git-send-email-yuanhan.liu@linux.intel.com> <111992201.GYQ3cgQmjX@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <111992201.GYQ3cgQmjX@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org, Victor Kaplansky , "Michael S. Tsirkin" Subject: Re: [dpdk-dev] [PATCH 0/5 for 2.3] vhost rxtx refactor 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, 18 Feb 2016 04:08:50 -0000 On Wed, Feb 17, 2016 at 11:50:22PM +0100, Thomas Monjalon wrote: > Hi Yuanhan, > > 2015-12-03 14:06, Yuanhan Liu: > > Vhost rxtx code is derived from vhost-switch example, which is very > > likely the most messy code in DPDK. Unluckily, the move also brings > > over the bad merits: twisted logic, bad comments. > > > > When I joined this team firstly, I was quite scared off by the messy > > and long vhost rxtx code. While adding the vhost-user live migration > > support, that I have to make fews changes to it, I then ventured to > > look at it again, to understand it better, in the meantime, to see if > > I can refactor it. > > > > And, here you go. > > There were several comments and a typo detected. > Please what is the status of this patchset? Hi Thomas, It was delayed; and I will address those comments and send out a new version recently. --yliu