From: Padam Jeet Singh <padam.singh@inventum.net>
To: users@dpdk.org
Cc: skhare@vmware.com
Subject: [dpdk-users] vmxnet3 RX VLAN Strip offload incorrect behaviour
Date: Tue, 27 Mar 2018 12:01:22 +0530 [thread overview]
Message-ID: <C1FD8794-4137-4D27-89DE-DEC48B6E8E36@inventum.net> (raw)
Hi,
When configuring the vmxnet3 based ethernet device, the RX VLAN Strip offload does not work as it usually does with other real NICs which support this function.
When configuring with rxmode.hw_vlan_strip = 1, the ipackets statistic does not increase when a VLAN ether type frame is received on the port and it is also not received on queue RX.
However, when configuring rxmode.hw_vlan_strip = 0 ,the ipackets statistic increases as well as frames arrives with VLAN header.
Though calling rte_eth_dev_set_vlan_offload(port, ETH_VLAN_STRIP_OFFLOAD) returns a success, however VLAN stripping on RX does not work.
TX VLAN INSERT offload on the other hand works just fine.
Is this a bug in vmxnet3 driver of dpdk?
Thanks,
Padam
reply other threads:[~2018-03-27 6:31 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=C1FD8794-4137-4D27-89DE-DEC48B6E8E36@inventum.net \
--to=padam.singh@inventum.net \
--cc=skhare@vmware.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).