From: Mark Bloch <mbloch@nvidia.com>
To: Qiyu Yan <yanqiyu17@mails.ucas.ac.cn>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Cc: netdev@vger.kernel.org, Ivan Vecera <ivecera@redhat.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [?bug] Can't get switchdev mode work on ConnectX-4 Card
Date: Tue, 22 Apr 2025 11:50:57 +0300 [thread overview]
Message-ID: <31146ec3-f581-423e-ab54-2d734d3ac42e@nvidia.com> (raw)
In-Reply-To: <131a4587-40d1-4cee-8f5f-52d9f6920034@mails.ucas.ac.cn>
On 22/04/2025 11:45, Qiyu Yan wrote:
> 在 2025/4/22 16:14, Mark Bloch 写道:
>> so you want to do QinQ (not sure cx4-lx supports qinq)
>> or just different vlans based on the traffic?
>> I don't think cx4-lx supports vlan push offloads.
> Just want to grant access to different vlans through a single VF, the command with ip
> $ ip link set <interface> vf X vlan Y
> filters and tags a single vlan. I am wondering if there is a suggested way to "pass-though" multiple vlans to a VM that I can create vlan interface in.
Usually you don't want the VF to be aware what vlans are used, on egress in the FDB you push vlan
and on ingress in the FDB you pop vlan. The VF gets the traffic without any vlans.
With the TC command I wrote you can match on mac (or ip, tcp, udp etc) and push/pop vlan as you want
and with as many different vlan as you want.
>
> Maybe this patch is for this: https://patchwork.ozlabs.org/project/netdev/cover/20170827110618.20599-1-saeedm@mellanox.com/ but it is not merged yet...
This patch is from 2017, it's not relevant.
mark
>
> Or I have to put the VF in promiscuous mode/pass-though multiple VFs?
>
> Qiyu
>
prev parent reply other threads:[~2025-04-22 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 9:07 [?bug] Can't get switchdev mode work on ConnectX-4 Card Qiyu Yan
2025-04-22 6:42 ` Mark Bloch
2025-04-22 7:15 ` Qiyu Yan
2025-04-22 8:14 ` Mark Bloch
2025-04-22 8:45 ` Qiyu Yan
2025-04-22 8:50 ` Mark Bloch [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=31146ec3-f581-423e-ab54-2d734d3ac42e@nvidia.com \
--to=mbloch@nvidia.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=yanqiyu17@mails.ucas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.