From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: [PATCH v12 0/6] add Tx preparation Date: Wed, 7 Dec 2016 18:18:33 +0800 Message-ID: <20161207101833.GL31182@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> <20161207081144.GC31182@yliu-dev.sh.intel.com> <2601191342CEEE43887BDE71AB9772583F0E4E4B@irsmsx105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Yigit, Ferruh" , Olivier Matz , Thomas Monjalon , "dev@dpdk.org" , Jan Medala , Jakub Palider , Netanel Belgazal , Evgeny Schemeilin , Alejandro Lucero , Yong Wang , Andrew Rybchenko , Hemant Agrawal , "Kulasek, TomaszX" To: "Ananyev, Konstantin" Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id F0A452B96 for ; Wed, 7 Dec 2016 11:17:51 +0100 (CET) Content-Disposition: inline In-Reply-To: <2601191342CEEE43887BDE71AB9772583F0E4E4B@irsmsx105.ger.corp.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 Wed, Dec 07, 2016 at 10:13:14AM +0000, Ananyev, Konstantin wrote: > > Hi Yliu, > > > > > 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. > > > > So would you like to provide a patch for it, > Or would you like to keep tx_prepare() for virtio as NOP for now? Hi Konstantin, I'd keep it as it is for now. It should be a trivial patch after all, that I could provide it when everything are settled down. --yliu