From: Roman Novikov <rnovikov@rdp.ru>
To: dev@dpdk.org
Subject: [dpdk-dev] VMDQ question
Date: Wed, 27 Mar 2019 12:14:06 +0300 [thread overview]
Message-ID: <9fd54440-1f13-0507-36b0-8b9d7d8508fb@rdp.ru> (raw)
Dear developers! I have some troubles with VDMQ configuring.
Goal: I want to split physical port to 2 virtual depend on vlan. I need
rss (32 queues on each virtual port, and 32 queues for untagged packets)
and keep LLDP, LACP/LAG functionality.
so i need 3 Rss group, each 32 queues (Untagged, Vlan A, Vlan B)
hardware and OS:
Xeon E5 2695 v4, X710 4X10Gb (firmware 6.8), Ubunti server 18.04 LTS,
dpdk 19.02
I am trying to configure VMDQ with rss.
DPDK config changes:
CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF=32
CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM=32
Then i configured 8 pools and all queues( queues, that i am not going to
use i configured with pool, that i am not going to use (to save some
memory))
Then i filled rte_eth_vmdq_rx_conf strcut. It has field "rx_mode", where
i set 0 ( so i set nither ETH_VMDQ_ACCEPT_UNTAG not
ETH_VMDQ_ACCEPT_BROADCAST );
I expect, that i will have packets with vlan Tag A on queues 32-63,
with Tag B qeueus 64-95 and UNTAG traffic on queues 0-31 with RSS.
It works, but some packets appear on each pool , like ( Ether(dst=
"ff:ff:ff:ff:ff:ff:ff")/IP(dst="255.255.255.255")).
I looked in i40e driver code, and found, that driver ignore field
"rx_mode".
Questions
1. Is it bug? If Yes, when it will be fixed?
2. Has this case workaround ? (maby i can do it with vlan mirroring? )
If Yes, can you help me with configuration? ( I will be glad to have
simple example with mirroring)
3. Maby i can fix it by myself? (so i need few words about, what should
i do?
next reply other threads:[~2019-03-27 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 9:14 Roman Novikov [this message]
2019-03-27 9:14 ` Roman Novikov
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=9fd54440-1f13-0507-36b0-8b9d7d8508fb@rdp.ru \
--to=rnovikov@rdp.ru \
--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).