From: "Wu, Xiaoban" <Xiaoban_Wu@student.uml.edu>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] A question about the macro "RTE_ETH_IS_IPV4_HDR" used in the example l3fwd-acl
Date: Thu, 19 Jan 2017 21:38:00 +0000 [thread overview]
Message-ID: <BN6PR02MB27062B33196C4E7F099A4488BC7E0@BN6PR02MB2706.namprd02.prod.outlook.com> (raw)
Dear DPDK users,
I am working on the l3fwd-acl example http://dpdk.org/doc/guides/sample_app_ug/l3_forward_access_ctrl.html.
I just find that the macro "RTE_ETH_IS_IPV4_HDR" used on line 699 and 752 of the main.c rejected all the normal UDP packets.
Hence, I want to know if the PMD driver is required to parse the packet and update the "packet_type" field in the "struct rte_mbuf" whenever the packet is received?
If the answer is yes, then the PMD "librte_pmd_mlx5" seems to fail to do so, since all the packet_type I got are all zero which are not the required 0x00000010.
If the answer is no, then there would be better some warning on the webpage.
Thank you very much!
Best wishes,
Xiaoban
reply other threads:[~2017-01-19 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN6PR02MB27062B33196C4E7F099A4488BC7E0@BN6PR02MB2706.namprd02.prod.outlook.com \
--to=xiaoban_wu@student.uml.edu \
--cc=dev@dpdk.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).