From: John Fastabend <john.fastabend@gmail.com>
To: Tariq Toukan <ttoukan.linux@gmail.com>,
Tariq Toukan <tariqt@mellanox.com>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Eran Ben Elisha <eranbe@mellanox.com>,
Moshe Shemesh <moshe@mellanox.com>
Subject: Re: [PATCH net-next V2 5/5] net/mlx4: Add VST QinQ support
Date: Wed, 27 Jul 2016 11:05:25 -0700 [thread overview]
Message-ID: <5798F7E5.1020309@gmail.com> (raw)
In-Reply-To: <653875ea-f06b-e850-d5d2-1c248b2341a6@gmail.com>
On 16-07-26 07:23 AM, Tariq Toukan wrote:
> Hi John,
>
> Currently we support one tag set to a VF by the administrator, with the
> new interface can be either C-VLAN or S-VLAN.
> Once S-VLAN is set by administrator, the VM can set the C-VLANs it wants
> to use.
>
> S-VLAN + C-VLAN per vf currently is not supported, but can be a future
> use case.
> Command line in such case should add more tuples of {vlan, qos, proto}
> such as:
> ip link set dev ens2 vf 0 vlan 100 qos 2 proto 802.1ad vlan 50 qos 4
> proto 802.1q
>
yep looks good to me.
> As we currently don't support it, we will change the new
> IFLA_VF_VLAN_INFO struct to include a list of such tuples and currently
> use only the first one.
> Is that what you meant?
>
Yep that was exactly my suggestion. Because I know hardware that
supports the double tag mode and as soon as someone sees they can
change the proto they will ask me to support double tags.
There are two approaches to this either make the struct understand
a list of tags or build it into the netlink message using netlink
TLV constructs. I'm OK with either approach take a look at the code
and see how it looks.
Thanks for working on this.
> Regards,
> Tariq and Moshe
>
prev parent reply other threads:[~2016-07-27 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 11:15 [PATCH net-next V2 0/5] mlx4 VST QinQ support Tariq Toukan
2016-07-25 11:15 ` [PATCH net-next V2 1/5] net/mlx4_core: Fix QUERY FUNC CAP flags Tariq Toukan
2016-07-25 11:15 ` [PATCH net-next V2 2/5] net/mlx4_core: Preparation for VST QinQ Tariq Toukan
2016-07-25 11:15 ` [PATCH net-next V2 3/5] net/mlx4_en: " Tariq Toukan
2016-07-25 11:15 ` [PATCH net-next V2 4/5] net: Update API for VST QinQ support Tariq Toukan
2016-07-25 11:15 ` [PATCH net-next V2 5/5] net/mlx4: Add " Tariq Toukan
2016-07-25 17:12 ` John Fastabend
[not found] ` <653875ea-f06b-e850-d5d2-1c248b2341a6@gmail.com>
2016-07-27 18:05 ` John Fastabend [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=5798F7E5.1020309@gmail.com \
--to=john.fastabend@gmail.com \
--cc=davem@davemloft.net \
--cc=eranbe@mellanox.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.com \
--cc=ttoukan.linux@gmail.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).