From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/mlx5: add workaround for VLAN in virtual machine
Date: Wed, 31 Jul 2019 06:14:24 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795A9410C9184D5C563B1FFC3DF0@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1564478424-7686-1-git-send-email-viacheslavo@mellanox.com>
Tuesday, July 30, 2019 12:20 PM, Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH v3] net/mlx5: add workaround for VLAN in
> virtual machine
>
> On some virtual setups (particularly on ESXi) when we have SR-IOV and E-
> Switch enabled there is the problem to receive VLAN traffic on VF interfaces.
> The NIC driver in ESXi hypervisor does not setup E-Switch vport setting
> correctly and VLAN traffic targeted to VF is dropped.
>
> The patch provides the temporary workaround - if the rule containing the
> VLAN pattern is being installed for VF the VLAN network interface over VF is
> created, like the command does:
>
> ip link add link vf.if name mlx5.wa.1.100 type vlan id 100
>
> The PMD in DPDK maintains the database of created VLAN interfaces for
> each existing VF and requested VLAN tags. When all of the RTE Flows using
> the given VLAN tag are removed the created VLAN interface with this VLAN
> tag is deleted.
>
> The name of created VLAN interface follows the format:
>
> evmlx.d1.d2, where d1 is VF interface ifindex, d2 - VLAN ifindex
>
> Implementation limitations:
>
> - mask in rules is ignored, rule must specify VLAN tags exactly,
> no wildcards (which are implemented by the masks) are allowed
>
> - virtual environment is detected via rte_hypervisor() call,
> and the type of hypervisor is checked. Currently we engage
> the workaround for ESXi and unrecognized hypervisors (which
> always happen on platforms other than x86 - it means workaround
> applied for the Flow over PCI VF). There are no confirmed data
> the other hypervisors (HyperV, Qemu) need this workaround,
> we are trying to reduce the list of configurations on those
> workaround should be applied.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Acked-by: Matan Azrad <matan@mellanox.com>
Acked-by: Shahaf Shuler <shahafs@mellanox.com>
next prev parent reply other threads:[~2019-07-31 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 13:45 [dpdk-dev] [PATCH] net/mlx5: fix ESXi " Viacheslav Ovsiienko
2019-07-29 15:14 ` Matan Azrad
2019-07-29 15:26 ` [dpdk-dev] [PATCH v2] " Viacheslav Ovsiienko
2019-07-30 5:05 ` Shahaf Shuler
2019-07-30 9:20 ` [dpdk-dev] [PATCH v3] net/mlx5: add workaround for " Viacheslav Ovsiienko
2019-07-31 6:14 ` Shahaf Shuler [this message]
2019-07-31 7:39 ` Raslan Darawsheh
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=AM0PR0502MB3795A9410C9184D5C563B1FFC3DF0@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=viacheslavo@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).