From: "Dey, Souvik" <sodey@rbbn.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "shahafs@mellanox.com" <shahafs@mellanox.com>,
"yskoh@mellanox.com" <yskoh@mellanox.com>
Subject: [dpdk-dev] Vlan not working with Mellanox NIC on VmWare
Date: Fri, 1 Oct 2021 18:31:26 +0000 [thread overview]
Message-ID: <DM6PR03MB4777EEC044B9A1B1EE3BBAF9CDAB9@DM6PR03MB4777.namprd03.prod.outlook.com> (raw)
Hi All,
We were trying to test the vlan filter with Melloanox nic(SR-IOV) on VmWare using the mlx5_pmd. But found that after doing the mlx5_vlan_filter_set with the vlan id also, we are not receiving the tagged packets upto the application. The same works fine in we are using KVM as the hypervisor. To check if this the PF deiver issue, we removed the dpdk and made the vlan config on the linux interface and then found that the tagged packets are coming upto the VM. Moreover the same tag which was used by linux kernel keeps working with DPDK too even after reboot o the VM but new tags added through DPDK does not work . Is it necessary to add the tags every time to the linux netdev before using it through dpdk ? Though this does not sound right.Can somebody help me in why with dpdk we are not able to receive the tagged packets ?
DPDK version : 18.11.6
ESXi : 7.0
NICs : Mellanox Cx-4
Just to summarize :
1. VLAN filter add through DPDK works fine with KVM hypervisor.
2. VLAN filter add through DPDK on VmWare does not work.
3. VLAN add through linux netdev works fine on VmWare
4. VLAN once added on the linux netdev, even after eboot the same VLAN added through dpdk works fine on VmWare. Any new VLAN added through dpdk does not work.
--
Regards,
Souvik
Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
reply other threads:[~2021-10-01 18: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=DM6PR03MB4777EEC044B9A1B1EE3BBAF9CDAB9@DM6PR03MB4777.namprd03.prod.outlook.com \
--to=sodey@rbbn.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=yskoh@mellanox.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).