From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id D9BF72B96 for ; Wed, 7 Dec 2016 09:11:02 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga105.jf.intel.com with ESMTP; 07 Dec 2016 00:11:01 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="199921226" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga004.fm.intel.com with ESMTP; 07 Dec 2016 00:10:59 -0800 Date: Wed, 7 Dec 2016 16:11:44 +0800 From: Yuanhan Liu To: Ferruh Yigit , Olivier Matz Cc: Thomas Monjalon , dev@dpdk.org, Jan Medala , Jakub Palider , Netanel Belgazal , Evgeny Schemeilin , Alejandro Lucero , Yong Wang , Andrew Rybchenko , Hemant Agrawal , Tomasz Kulasek , konstantin.ananyev@intel.com Message-ID: <20161207081144.GC31182@yliu-dev.sh.intel.com> References: <1477486575-25148-1-git-send-email-tomaszx.kulasek@intel.com> <1479922585-8640-1-git-send-email-tomaszx.kulasek@intel.com> <8317180.L80Qf11uiu@xps13> <2dfc10d2-bb19-1385-aa01-97e44a3db139@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2dfc10d2-bb19-1385-aa01-97e44a3db139@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v12 0/6] add Tx preparation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 08:11:03 -0000 On Tue, Dec 06, 2016 at 03:53:42PM +0000, Ferruh Yigit wrote: > > Please, we need a comment for each driver saying > > "it is OK, we do not need any checksum preparation for TSO" > > or > > "yes we have to implement tx_prepare or TSO will not work in this mode" > > Sorry for late. For virtio, I think it's not a must. The checksum stuff has been handled inside the Tx function. However, we may could move it to tx_prepare, which would actually recover the performance lost introduced while enabling TSO for the non-TSO case. --yliu