From: longtb5@viettel.com.vn
To: <mb@smartsharesystems.com>, <roszenrami@gmail.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] [RFC] function to parse packet headers
Date: Wed, 9 Jan 2019 10:43:16 +0700 (ICT) [thread overview]
Message-ID: <002301d4a7ce$d095b240$71c116c0$@viettel.com.vn> (raw)
Hi Morten,
What is the difference compare to rte_net_get_ptype(), which also parses
packet types and reports on header length.
In my application I have also done something similar about malformed
packets. IMO it's very useful to have return value indicate different types
of malformed packets, not just -1, e.g. invalid IP options, IP loopback,
etc.
Regards,
BL
next reply other threads:[~2019-01-09 3:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 3:43 longtb5 [this message]
2019-01-09 15:38 ` Morten Brørup
2019-01-10 3:25 ` longtb5
2019-01-10 8:21 ` Morten Brørup
-- strict thread matches above, loose matches on Subject: below --
2019-01-08 16:48 Morten Brørup
2019-01-08 20:09 ` Rami Rosen
2019-01-09 15:53 ` Morten Brørup
2019-01-09 23:57 ` Thomas Monjalon
2019-01-10 1:03 ` Rami Rosen
2019-01-11 0:11 ` Stephen Hemminger
2019-01-11 7:56 ` Andrew Rybchenko
2019-01-11 8:16 ` Morten Brørup
2019-01-11 8:28 ` Andrew Rybchenko
2019-01-11 8:35 ` Olivier Matz
2019-01-11 9:49 ` Ananyev, Konstantin
2019-01-11 12:04 ` Morten Brørup
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='002301d4a7ce$d095b240$71c116c0$@viettel.com.vn' \
--to=longtb5@viettel.com.vn \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=roszenrami@gmail.com \
/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).