From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH 6/6] examples/vhost: add an option to enable Tx zero copy Date: Tue, 23 Aug 2016 20:33:21 +0800 Message-ID: <20160823123321.GL30752@yliu-dev.sh.intel.com> References: <1471939839-29778-1-git-send-email-yuanhan.liu@linux.intel.com> <1471939839-29778-7-git-send-email-yuanhan.liu@linux.intel.com> <2052249.1FX31XPDFZ@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, Maxime Coquelin To: Thomas Monjalon Return-path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 778143239 for ; Tue, 23 Aug 2016 14:23:36 +0200 (CEST) Content-Disposition: inline In-Reply-To: <2052249.1FX31XPDFZ@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Aug 23, 2016 at 11:31:08AM +0200, Thomas Monjalon wrote: > 2016-08-23 16:10, Yuanhan Liu: > > One thing worth noting while using Tx zero copy is the nb_tx_desc has > > to be small enough so that the eth driver will hit the mbuf free > > threshold easily and thus free mbuf more frequently. > > > > The reason behind that is, when Tx zero copy is enabled, guest Tx used > > vring will be updated only when corresponding mbuf is freed. If mbuf is > > not freed frequently, the guest Tx vring could be starved. > > I think you should explain this behaviour in the doc of the vhost flag. Agreed. Will do it in v2. --yliu