From: John Sucaet <john.sucaet@oneaccess-net.com>
To: <users@dpdk.org>
Subject: [dpdk-users] Receiving dot1Q frames on VF with I350 in SR-IOV
Date: Wed, 3 Oct 2018 17:26:42 +0200 [thread overview]
Message-ID: <80d66c28-5914-632c-a9e9-9f98011bc5b8@oneaccess-net.com> (raw)
Hi,
Our dpdk (17.05) application runs in a virtual machine (VM, qemu/kvm).
One VF of a i350 NIC in SR-IOV mode (max_vfs=7) is provided to this VM.
The host (Fedora 25) has the latest igb driver (5.3.5.20).
We see a problem when trying to send or to receive frames with 802.1Q
tagging. We send the VLAN tagged frames from the application with the
VLAN header already inserted and want to receive frames without the VLAN
header being stripped. We don't configure hw filtering (hw_vlan_filter =
0 in rxmode). We don't see any packet leaving the VM, unless we disable
on the host vlan spoof checking (ip link set enp10s0f0 vf 0 spoofchk
off). However on the rx side, tagged packets are not sent to the VF, but
seen in a tcpdump on the PF.
My questions: has this to do with vlan promiscuous mode which is not
enabled by the igb driver? Is it possible to enable vlan promiscuous
mode from the VM? If not, can I program the vlan filtering table from
the VM? (is that with the function: rte_eth_dev_vlan_filter?) Can I
disable vlan stripping/insertion from the VM?
Thanks for any help
John
reply other threads:[~2018-10-03 15:26 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=80d66c28-5914-632c-a9e9-9f98011bc5b8@oneaccess-net.com \
--to=john.sucaet@oneaccess-net.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).