From: Levend Sayar <levendsayar@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] mbuf->packet_type
Date: Mon, 2 Nov 2020 13:45:57 +0300 [thread overview]
Message-ID: <CAGDw98mg6d=RdzYXzex_0wgLUx-WxZ_wsJsM9jimbtGSpOL+aw@mail.gmail.com> (raw)
Hi all.
Recently I encountered a dont-know-why issue about mbuf->packet_type.
Two different setups behave differently.
One is a bare metal server, one KVM based OpenStack VM (virtio).
Both use the uio driver. Namely only hardware is different. Software stack
is the same.
But this macro does not work on OpenStack platform.
*RTE_ETH_IS_IPV4_HDR(mbuf->packet_type))*
where
*#define RTE_ETH_IS_IPV4_HDR(ptype) ((ptype) & RTE_PTYPE_L3_IPV4)*
I manually coded to check IPv4 like this:
*struct rte_ether_hdr* ether_hdr = rte_pktmbuf_mtod(mbuf, struct
rte_ether_hdr*);uint16_t ether_type = N2H16(ether_hdr->ether_type);if
(likely(ether_type == RTE_ETHER_TYPE_IPV4)) {*
Do you have any idea about this?
I suppose whoever fills that mbuf data packet_type field is not working in
a virtual environment.
Which entity fills that fields? Hardware driver, uio, dpdk?
Best,
Levend
next reply other threads:[~2020-11-02 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 10:45 Levend Sayar [this message]
2020-11-03 7:32 ` Levend Sayar
2020-11-03 8:02 ` Juhamatti Kuusisaari
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='CAGDw98mg6d=RdzYXzex_0wgLUx-WxZ_wsJsM9jimbtGSpOL+aw@mail.gmail.com' \
--to=levendsayar@gmail.com \
--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).