From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 2/2] mbuf: improve API doc for tunnel Tx offloads Date: Mon, 23 Apr 2018 10:53:17 +0200 Message-ID: <38112584.aOSrxqkTeH@xps> References: <20180420001324.11813-1-thomas@monjalon.net> <20180420001324.11813-3-thomas@monjalon.net> <20180423081449.yxyc2cbuhfavfeor@platinum> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, xuemingl@mellanox.com, harish.patil@cavium.com To: Olivier Matz Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id BB4F2F04 for ; Mon, 23 Apr 2018 10:53:19 +0200 (CEST) In-Reply-To: <20180423081449.yxyc2cbuhfavfeor@platinum> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 23/04/2018 10:14, Olivier Matz: > On Fri, Apr 20, 2018 at 02:13:24AM +0200, Thomas Monjalon wrote: > > + * These flags can be used with PKT_TX_TCP_SEG for TSO, or PKT_TX_xxx_CKSUM. > > + * The mbuf fields for inner and outer header lengths may be required: > > may be -> are > > > + * outer_l2_len, outer_l3_len, l2_len, l3_len, l4_len. > > and tso_segsz for TSO. >>From a HW point of view, some header lengths may be omitted if they are guessed by the HW. But you are right, from an API point of view, we should require them, no matter what is the underlying hardware. So the sentence becomes: * The mbuf fields for inner and outer header lengths are required: * outer_l2_len, outer_l3_len, l2_len, l3_len, l4_len and tso_segsz for TSO.