From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id E08578E01 for ; Thu, 11 Jan 2018 19:38:47 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Jan 2018 10:38:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,345,1511856000"; d="scan'208";a="9415462" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.48]) ([10.237.220.48]) by fmsmga002.fm.intel.com with ESMTP; 11 Jan 2018 10:38:44 -0800 To: Xueming Li , Olivier MATZ , Thomas Monjalon , Jingjing Wu , Yongseok Koh Cc: Shahaf Shuler , dev@dpdk.org References: <20180109141110.146250-1-xuemingl@mellanox.com> <20180109141110.146250-5-xuemingl@mellanox.com> From: Ferruh Yigit Message-ID: <340dbda2-e6a0-bd9c-3685-290d6554f06f@intel.com> Date: Thu, 11 Jan 2018 18:38:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180109141110.146250-5-xuemingl@mellanox.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 4/6] ethdev: introduce TX common tunnel offloads 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: Thu, 11 Jan 2018 18:38:48 -0000 On 1/9/2018 2:11 PM, Xueming Li wrote: > This patch introduce new DEV_TX_OFFLOAD_GENERIC_TNL_CKSUM_TSO flag for > devices that support tunnel agnostic TX checksum and tso offloading. > > Checksum offset and TSO header length are calculated based on mbuf > inner length l*_len, outer_l*_len and tx offload flags PKT_TX_*, tunnel > header length is part of inner l2_len, so device HW do cheksum and TSO > calculation w/o knowledge of perticular tunnel type. > > When set application must guarantee that correct header types and > lengths for each inner and outer headers in mbuf header, no need to > specify tunnel type. > > Signed-off-by: Xueming Li Acked-by: Ferruh Yigit