From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Matz Subject: Re: [PATCH 2/2] mbuf: improve API doc for tunnel Tx offloads Date: Mon, 23 Apr 2018 11:03:48 +0200 Message-ID: <20180423090348.kbryof7kpu6t4spy@platinum> References: <20180420001324.11813-1-thomas@monjalon.net> <20180420001324.11813-3-thomas@monjalon.net> <20180423081449.yxyc2cbuhfavfeor@platinum> <38112584.aOSrxqkTeH@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, xuemingl@mellanox.com, harish.patil@cavium.com To: Thomas Monjalon Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 7C0191F1C for ; Mon, 23 Apr 2018 11:03:53 +0200 (CEST) Content-Disposition: inline In-Reply-To: <38112584.aOSrxqkTeH@xps> 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 Mon, Apr 23, 2018 at 10:53:17AM +0200, Thomas Monjalon wrote: > 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. Sounds good, thanks.