From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: rte_mbuf's packet_type field Date: Fri, 4 Mar 2016 10:28:39 +0100 Message-ID: <56D95547.8080601@6wind.com> References: <56D5CE1B.2070002@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Zoltan Kiss , dev@dpdk.org Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 45AE42BF5 for ; Fri, 4 Mar 2016 10:28:45 +0100 (CET) In-Reply-To: <56D5CE1B.2070002@linaro.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Zoltan, On 03/01/2016 06:15 PM, Zoltan Kiss wrote: > I have a quick question about this field: how do I know if the > underlying PMD supports a particular protocol parsing. Let's say I want > to check for SCTP packets, looking at this field tells me EITHER the > packet is SCTP (or not), OR that the hardware has no idea about SCTP. Is > there a way to figure that support out? I'm not aware of such a feature. I guess you want to avoid to re-check all protocols in software if the hardware supports some of them and did not recognize them? In that case it may be interesting, but it would result in a lot of feature flags. Regards, Olivier