From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>,
Zoltan Kiss <zoltan.kiss@linaro.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] rte_mbuf's packet_type field
Date: Fri, 4 Mar 2016 10:58:21 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B162E0@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <56D95547.8080601@6wind.com>
Hi,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ
> Sent: Friday, March 04, 2016 9:29 AM
> To: Zoltan Kiss; dev@dpdk.org
> Subject: Re: [dpdk-dev] rte_mbuf's packet_type field
>
> 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.
Nothing in the mainline, but there is a patches in-flight:
http://dpdk.org/dev/patchwork/patch/10921/
Konstantin
>
> Regards,
> Olivier
next prev parent reply other threads:[~2016-03-04 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 17:15 Zoltan Kiss
2016-03-04 9:28 ` Olivier MATZ
2016-03-04 10:58 ` Ananyev, Konstantin [this message]
2016-03-04 13:40 ` Zoltan Kiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2601191342CEEE43887BDE71AB97725836B162E0@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=zoltan.kiss@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).