From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id A452C2E8D for ; Wed, 7 Jan 2015 10:59:25 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP; 07 Jan 2015 01:56:06 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,713,1413270000"; d="scan'208";a="633671293" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga001.jf.intel.com with ESMTP; 07 Jan 2015 01:59:23 -0800 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.195]) by IRSMSX108.ger.corp.intel.com ([169.254.11.71]) with mapi id 14.03.0195.001; Wed, 7 Jan 2015 09:59:22 +0000 From: "Ananyev, Konstantin" To: "Liu, Jijiang" , 'Olivier MATZ' Thread-Topic: [dpdk-dev] [PATCH v3 0/3] enhance TX checksum command and csum forwarding engine Thread-Index: AQHQFSvOf5ZHcwOIQ0S6LPFf4KIhoZyLUqAAgADVrYCAJ+m7AIAAhGKA Date: Wed, 7 Jan 2015 09:59:22 +0000 Message-ID: <2601191342CEEE43887BDE71AB977258213D337B@irsmsx105.ger.corp.intel.com> References: <1418173403-30202-1-git-send-email-jijiang.liu@intel.com> <54896F4A.4070601@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DA1B70@SHSMSX101.ccr.corp.intel.com> <548B18C9.3020408@6wind.com> <1ED644BD7E0A5F4091CF203DAFB8E4CC01DA7699@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC01DA7699@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v3 0/3] enhance TX checksum command and csum forwarding engine 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: Wed, 07 Jan 2015 09:59:26 -0000 Hi Frank, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Liu, Jijiang > Sent: Wednesday, January 07, 2015 2:04 AM > To: 'Olivier MATZ' > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v3 0/3] enhance TX checksum command and cs= um forwarding engine >=20 > Hi Olivier, >=20 > > -----Original Message----- > > From: Olivier MATZ [mailto:olivier.matz@6wind.com] > > Sent: Saturday, December 13, 2014 12:33 AM > > To: Liu, Jijiang > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH v3 0/3] enhance TX checksum command and > > csum forwarding engine > > > > Hello, > > > > On 12/12/2014 04:48 AM, Liu, Jijiang wrote: > > > The 'hw/sw' option is used to set/clear the flag of enabling TX tunn= eling packet > > checksum hardware offload in testpmd application. > > > > This is not clear at all. > > In your command, there is (hw|sw|none). > > Are you talking about inner or outer? > > Is this command useful for any kind of packet? > > How does it combine with "tx_checksum set outer-ip (hw|sw)"? > > >=20 > I rethink these TX checksum commands in this patch set and agree with you= that we should make some changes for having clear > meaning for them. >=20 > There are 3 commands in patch set as follows, > 1. tx_checksum set tunnel (hw|sw|none) (port-id) >=20 > Now I also think the command 1 may confuse user, they probably don't unde= rstand why we need 'hw' or 'sw' option and when to > use the two option, > so I will replace the command with 'tx_checksum set hw-tunnel-mode (on|of= f) (port-id)' command. I am a bit confused here, could you explain what would be a behaviour for '= on' and 'off'? Konstantin >=20 > 2. tx_checksum set outer-ip (hw|sw) (port-id) > 3. tx_checksum set (ip|udp|tcp|sctp) (hw|sw) (port-id) >=20 > The command 2 will be merged into command 3, the new command is ' tx_chec= ksum set (outer-ip|ip|udp|tcp|sctp) (hw|sw) (port- > id)'. >=20 > These most of the cases in http://dpdk.org/ml/archives/dev/2014-December/= 009213.html will be covered by using the two > commands >=20 > The command 'tx_checksum set hw-tunnel-mode (on|off) (port-id)' is used = to set/clear TESTPMD_TX_OFFLOAD_TUNNEL_CKSUM > flag. > Actually, the PKT_TX_UDP_TUNNEL_PKT offload flag will be set if the testp= md flag is set, which tell driver/HW treat that transmit > packet as a tunneling packet. >=20 > When 'on' is set, which is able to meet Method B.1 and method C. >=20 > When 'off' is set, the TESTPMD_TX_OFFLOAD_TUNNEL_CKSUM is not needed to s= et, so the PKT_TX_UDP_TUNNEL_PKT offload flag is > not needed to set, then HW treat that transmit packet as a non-tunnelin= g packet. It is able to meet Method B.2. >=20 > As to case A, I think it is not mandatory to cover it in csum fwd engine = for tunneling packet. >=20 > Is the above description clear for you? >=20 > > Regards, > > Olivier