From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ophir Munk Subject: Re: [PATCH v1] gso: fix marking TCP checksum flag in TCP segments Date: Tue, 24 Apr 2018 13:53:22 +0000 Message-ID: References: <1524406859-29585-1-git-send-email-ophirmu@mellanox.com> <2601191342CEEE43887BDE71AB977258AEA5081C@IRSMSX102.ger.corp.intel.com> <2601191342CEEE43887BDE71AB977258AEA5221E@IRSMSX102.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: Thomas Monjalon , Olga Shern , Pascal Mazon , "stable@dpdk.org" To: "Hu, Jiayu" , "Ananyev, Konstantin" , "dev@dpdk.org" Return-path: In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Jiayu, > -----Original Message----- > From: Hu, Jiayu [mailto:jiayu.hu@intel.com] > Sent: Tuesday, April 24, 2018 3:56 PM > To: Ananyev, Konstantin ; Ophir Munk > ; dev@dpdk.org > Cc: Thomas Monjalon ; Olga Shern > ; Pascal Mazon ; > stable@dpdk.org > Subject: RE: [PATCH v1] gso: fix marking TCP checksum flag in TCP segment= s >=20 > Hi Konstantin and Ophir, >=20 ...=20 > > Another possibility - might be make chages in librte_gso to allow user > > to specify what flags to set for the output packets (probably via > > rte_gso_ctx.flag) >=20 > It would be a solution. We can add flags to rte_gso_ctx.flag and the GSO > library can do some extra work (like checksum) according to the flags. >=20 I think that calculating TCP checksums by GSO library should be optional (i= f at all).=20 In my case I prefer TAP PMD to do the work which is TAP-specific. =20 My original intention in this patch was only to mark PKT_TX_TCP_CKSUM flag. > Thanks, > Jiayu > > > > Konstantin > > ...