From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dai, Wei" Subject: Re: [PATCH] examples/ip_fragmentation: fix check of packet type Date: Mon, 13 Mar 2017 07:56:08 +0000 Message-ID: <49759EB36A64CF4892C1AFEC9231E8D63A377662@PGSMSX106.gar.corp.intel.com> References: <1489116490-2490-1-git-send-email-wei.dai@intel.com> <2601191342CEEE43887BDE71AB9772583FACD1BD@IRSMSX109.ger.corp.intel.com> <49759EB36A64CF4892C1AFEC9231E8D63A377512@PGSMSX106.gar.corp.intel.com> <2601191342CEEE43887BDE71AB9772583FACE36C@IRSMSX109.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "stable@dpdk.org" To: "Ananyev, Konstantin" , "dev@dpdk.org" Return-path: In-Reply-To: <2601191342CEEE43887BDE71AB9772583FACE36C@IRSMSX109.ger.corp.intel.com> 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" > -----Original Message----- > From: Ananyev, Konstantin > Sent: Monday, March 13, 2017 3:02 PM > To: Dai, Wei ; dev@dpdk.org > Cc: stable@dpdk.org > Subject: RE: [PATCH] examples/ip_fragmentation: fix check of packet type >=20 > Hi Wei, >=20 > > > > Hi, Konstantin > > I see your point. > > I think your method can work. > > But I think your method is a bit complex. As you method need to add mor= e > codes. > > Anyway this is a simple bug. > > How do you think now ? >=20 > I still think it is better for all apps to handle this issue in a uniform= way. > Again in that case for NICs that do support PTYPE offloads the performanc= e > should be unaffected. > Konstantin >=20 I have just had a quick look through the l3fwd and didn't find any codes to= =20 check what ptypes capabilities ae provided by stuff below DPDK PMD & its ba= se driver. L3fwd only check an input argument "--parse-ptype" to enable ptype check im= plemented in a Rx callback function. In this l3fwd rx callback function, it has done the same thing as my code. Anyway, I'd like to provide a v2 patch to deal with this issue in a uniform= way. Thanks & Best Regards -Wei