From: Volodymyr Veskera <volodymyrv@interfacemasters.com>
To: users@dpdk.org
Subject: [dpdk-users] VLAN tci is not saved in rte_mbuf after HW stripping on X710/XL710
Date: Fri, 9 Aug 2019 19:18:32 +0300 [thread overview]
Message-ID: <CAJxd2g1WoPHt-iCK4um49QCLCLAKMt_mxBOh5kW53NTdXKTy5Q@mail.gmail.com> (raw)
Hello,
I am using XL710 card (FW version - 6.01 0x800034aa 0.0.0, DPDK version -
18.02.2 stable) and faced the next issue:
When VLAN offload feature is configured, in the fist packet provided by the
PMD (after hardware vlan stripping) vlan tci is not saved in
mbuf->vlan_tci. While ol_flags = 451, which tells that PKT_RX_VLAN_STRIPPED
and PKT_RX_VLAN flags were set.
Second and all next packets have correct mbuf->vlan_tci.
This issue reproduces only for VLAN tagged packets with length >= 2000
bytes.
If I am using rte_vlan_strip() for software vlan stripping, I do not see
such a problem.
Please share your thoughts about this.
Regards,
Volodymyr
reply other threads:[~2019-08-09 16:18 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=CAJxd2g1WoPHt-iCK4um49QCLCLAKMt_mxBOh5kW53NTdXKTy5Q@mail.gmail.com \
--to=volodymyrv@interfacemasters.com \
--cc=users@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).