From: Stephen Hemminger <stephen@networkplumber.org>
To: Tariq Toukan <tariqt@mellanox.com>
Cc: netdev@vger.kernel.org, Eran Ben Elisha <eranbe@mellanox.com>,
John Fastabend <john.fastabend@gmail.com>,
Moshe Shemesh <moshe@mellanox.com>
Subject: Re: [PATCH iproute2] ip link: Add support to configure SR-IOV VF to vlan protocol 802.1ad (VST QinQ)
Date: Sun, 9 Oct 2016 19:24:34 -0700 [thread overview]
Message-ID: <20161009192434.04902ca0@xeon-e3> (raw)
In-Reply-To: <1475049539-25905-1-git-send-email-tariqt@mellanox.com>
On Wed, 28 Sep 2016 10:58:59 +0300
Tariq Toukan <tariqt@mellanox.com> wrote:
> From: Moshe Shemesh <moshe@mellanox.com>
>
> Introduce a new API that exposes a list of vlans per VF (IFLA_VF_VLAN_LIST),
> giving the ability for user-space application to specify it for the VF as
> an option to support 802.1ad (VST QinQ).
>
> We introduce struct vf_vlan_info, which extends struct vf_vlan and adds
> an optional VF VLAN proto parameter.
> Default VLAN-protocol is 802.1Q.
>
> Add IFLA_VF_VLAN_LIST in addition to IFLA_VF_VLAN to keep backward
> compatibility with older kernel versions.
>
> Suitable ip link tool command examples:
> - Set vf vlan protocol 802.1ad (S-TAG)
> ip link set eth0 vf 1 vlan 100 proto 802.1ad
> - Set vf vlan S-TAG and vlan C-TAG (VST QinQ)
> ip link set eth0 vf 1 vlan 100 proto 802.1ad vlan 30 proto 802.1Q
> - Set vf to VST (802.1Q) mode
> ip link set eth0 vf 1 vlan 100 proto 802.1Q
> - Or by omitting the new parameter (backward compatible)
> ip link set eth0 vf 1 vlan 100
>
> Signed-off-by: Moshe Shemesh <moshe@mellanox.com>
> Signed-off-by: Tariq Toukan <tariqt@mellanox.com>
Applied to net-next (for 4.9)
prev parent reply other threads:[~2016-10-10 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 7:58 [PATCH iproute2] ip link: Add support to configure SR-IOV VF to vlan protocol 802.1ad (VST QinQ) Tariq Toukan
2016-10-10 2:24 ` Stephen Hemminger [this message]
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=20161009192434.04902ca0@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=eranbe@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@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).