From: Shun Hao <shunh@nvidia.com>
To: <matan@nvidia.com>, <viacheslavo@nvidia.com>,
<orika@nvidia.com   >, <thomas@monjalon.net >
Cc: <dev@dpdk.org  >, <rasland@nvidia.com>
Subject: [PATCH v2 0/2] Get E-Switch Manager vport ID
Date: Fri, 18 Feb 2022 09:45:54 +0200 [thread overview]
Message-ID: <20220218074556.25036-1-shunh@nvidia.com> (raw)
One of the E-Switch vports plays the special role - it is assigned as
"E-Switch manager" and has some special exclusive rights and duties - it
maintains all the representors, manages FDB domain flows, etc. By
default, the E-Switch vport index was supposed to be zero on standalone
NICs (regular ConnectX) and 0xFFFE SmartNIC (BlueField), but that was
not always correct - this index can be assigned with any value by
kernel/hypervisor.
To handle this and do not suggest any default values we should use DevX
API to query E-Switch manager vport ID directly from firmware, to make
sure we always use the correct value.
Shun Hao (2):
common/mlx5: query E-Switch manager vport ID
net/mlx5: new method to get E-Switch manager vport ID
drivers/common/mlx5/mlx5_devx_cmds.c | 12 ++++++++++++
drivers/common/mlx5/mlx5_devx_cmds.h | 2 ++
drivers/common/mlx5/mlx5_prm.h | 12 ++++++++++++
drivers/net/mlx5/mlx5_flow_dv.c | 4 ++++
4 files changed, 30 insertions(+)
--
2.20.0
next reply other threads:[~2022-02-18 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 7:45 Shun Hao [this message]
2022-02-18 7:45 ` [PATCH v2 1/2] common/mlx5: query E-Switch manager " Shun Hao
2022-02-18 7:45 ` [PATCH v2 2/2] net/mlx5: new method to get " Shun Hao
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=20220218074556.25036-1-shunh@nvidia.com \
--to=shunh@nvidia.com \
--cc=dev@dpdk.org  \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com   \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.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).