From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 6826E2C06 for ; Thu, 24 Mar 2016 15:58:08 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP; 24 Mar 2016 07:58:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,385,1455004800"; d="scan'208";a="770679604" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.85]) by orsmga003.jf.intel.com with SMTP; 24 Mar 2016 07:58:05 -0700 Received: by (sSMTP sendmail emulation); Thu, 24 Mar 2016 14:58:04 +0025 Date: Thu, 24 Mar 2016 14:58:04 +0000 From: Bruce Richardson To: Zhe Tao Cc: dev@dpdk.org, jingjing.wu@intel.com Message-ID: <20160324145804.GF13728@bricha3-MOBL3> References: <1458652425-6167-1-git-send-email-zhe.tao@intel.com> <1458703670-19898-1-git-send-email-zhe.tao@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1458703670-19898-1-git-send-email-zhe.tao@intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v2] i40e: fix ipv6 TSO issue for tx function 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, 24 Mar 2016 14:58:08 -0000 On Wed, Mar 23, 2016 at 11:27:50AM +0800, Zhe Tao wrote: > Issue: > when using the following CLI in testpmd to enable ipv6 TSO feature > ============= > set verbose 1 > csum set ip hw 0 > csum set udp hw 0 > csum set tcp hw 0 > csum set sctp hw 0 > csum set outer-ip hw 0 > csum parse_tunnel on 0 > tso set 800 0 > set fwd csum > > start > ============= > > We will not get we want, the ipv6 packets sent out from IXIA can be received by > i40e, but cannot forward to another port. > The root cause is when HW doing the TSO offload for packets, it not only depends > on the context descriptor to define the MSS and TSO payload size, it also > need to know whether this packets is ipv4 or ipv6, ipv4 need the header csum, > but ipv6 doesn't need the csum. We need to use the i40e_txd_enable_checksum to > set the ipv6 type flag into the data descriptor when the packets are for > ipv6 TSO. > > Fixes: e3f0151f (i40e: enable Tx checksum only for offloaded packets) > > Signed-off-by: Zhe Tao > --- > v2: change condition check for ipv6 TSO checksum offload > use a more clear check method which include both ipv4 & ipv6 TSO > > > drivers/net/i40e/i40e_rxtx.c | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/drivers/net/i40e/i40e_rxtx.c b/drivers/net/i40e/i40e_rxtx.c > index 1488f2f..3422ec2 100644 > --- a/drivers/net/i40e/i40e_rxtx.c > +++ b/drivers/net/i40e/i40e_rxtx.c > @@ -73,9 +73,16 @@ > > #define I40E_TXD_CMD (I40E_TX_DESC_CMD_EOP | I40E_TX_DESC_CMD_RS) > > +/* need to add the TSO flag to the checksum offload mask > + * even the packets like ipv6 doesn't need the checksum for ip header > + * but the FW need to know whether this TCP packets is ipv4 or ipv6, > + * so add this kind of information in the checksum offload field in the > + * normal data descriptor. > + */ > #define I40E_TX_CKSUM_OFFLOAD_MASK ( \ > PKT_TX_IP_CKSUM | \ > PKT_TX_L4_MASK | \ > + PKT_TX_TCP_SEG | \ > PKT_TX_OUTER_IP_CKSUM) > > static uint16_t i40e_xmit_pkts_simple(void *tx_queue, > -- To be honest, I'm a little confused by the patch description and the comment added into the code. The commit message talks about flagging to the HW whether a packet is IPv4 or IPv6. However, the change made is to add a TCP segmentation bit to an offload mask - something that seems irrelevant to telling if something is IPv4 or v6. As for the comment itself. The comment reads like a commit message for a patch, rather than as the comment on a macro. The comment talks exclusively about the TSO part of the mask, and ignores the other values in it. It also suffers the same problem as the commit message of not explaining how a TSO flag ties in with identifying IPv4 or v6. Could you please reword the commit message and rework the comment to be a proper comment on the whole macro and resubmit the patch. Thanks, /Bruce