From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [PATCH] mbuf: add IGMP packet type Date: Wed, 29 Aug 2018 22:10:27 +0530 Message-ID: <20180829164026.GA13511@jerin> References: <20180827123835.27531-1-jerin.jacob@caviumnetworks.com> <20180829083110.42d85024@xeon-e3> <20180829155904.GA7133@jerin> <20180829093436.3f06421f@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, olivier.matz@6wind.com To: Stephen Hemminger Return-path: Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0067.outbound.protection.outlook.com [104.47.41.67]) by dpdk.org (Postfix) with ESMTP id 1FCD0F11 for ; Wed, 29 Aug 2018 18:40:46 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20180829093436.3f06421f@xeon-e3> 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----- > Date: Wed, 29 Aug 2018 09:34:36 -0700 > From: Stephen Hemminger > To: Jerin Jacob > Cc: dev@dpdk.org, olivier.matz@6wind.com > Subject: Re: [dpdk-dev] [PATCH] mbuf: add IGMP packet type > > External Email > > On Wed, 29 Aug 2018 21:29:05 +0530 > Jerin Jacob wrote: > > > -----Original Message----- > > > Date: Wed, 29 Aug 2018 08:31:10 -0700 > > > From: Stephen Hemminger > > > To: Jerin Jacob > > > Cc: dev@dpdk.org, olivier.matz@6wind.com > > > Subject: Re: [dpdk-dev] [PATCH] mbuf: add IGMP packet type > > > > > > External Email > > > > > > On Mon, 27 Aug 2018 18:08:35 +0530 > > > Jerin Jacob wrote: > > > > > > > Add support for IGMP packet type. > > > > > > > > Signed-off-by: Jerin Jacob > > > > > > Could you add logic to recoginize IGMP to the software packet type identification > > > rte_net_get_ptype used by drivers that don't have hardware support. > > > > If everyone agrees then I can do it as adding IGMP support will reduce > > the performance of rte_net_get_ptype() and most of the NIC may not need it. > > > > Opinions? > > > > > > > > Also shouldn't this bit be part of RTE_PTYPE_L4_MASK? > > > > The RTE_PTYPE_L4_MASK is 0x00000f00 so it is part it. Right? > > Then you must add it to the software matcher since most drivers are advertising L4_MASK Which driver returns .dev_supported_ptypes_get ethdev ops with L4_MASK? >