From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Mark Bloch <mbloch@nvidia.com>,
linux-api@vger.kernel.org, linux-rdma@vger.kernel.org,
Maor Gottlieb <maorg@nvidia.com>
Subject: Re: [PATCH rdma-next v2] RDMA/mlx5: Expose private query port
Date: Thu, 8 Apr 2021 15:54:12 -0300 [thread overview]
Message-ID: <20210408185412.GA678376@nvidia.com> (raw)
In-Reply-To: <20210401085004.577338-1-leon@kernel.org>
On Thu, Apr 01, 2021 at 11:50:04AM +0300, Leon Romanovsky wrote:
> From: Mark Bloch <mbloch@nvidia.com>
>
> Expose a non standard query port via IOCTL that will be used to expose
> port attributes that are specific to mlx5 devices.
>
> The new interface receives a port number to query and returns a
> structure that contains the available attributes for that port.
> This will be used to fill the gap between pure DEVX use cases
> and use cases where a kernel needs to inform userspace about
> various kernel driver configurations that userspace must use
> in order to work correctly.
>
> Flags is used to indicate which fields are valid on return.
>
> MLX5_IB_UAPI_QUERY_PORT_VPORT:
> The vport number of the queered port.
>
> MLX5_IB_UAPI_QUERY_PORT_VPORT_VHCA_ID:
> The VHCA ID of the vport of the queered port.
>
> MLX5_IB_UAPI_QUERY_PORT_VPORT_STEERING_ICM_RX:
> The vport's RX ICM address used for sw steering.
>
> MLX5_IB_UAPI_QUERY_PORT_VPORT_STEERING_ICM_TX:
> The vport's TX ICM address used for sw steering.
>
> MLX5_IB_UAPI_QUERY_PORT_VPORT_REG_C0:
> The metadata used to tag egress packets of the vport.
>
> MLX5_IB_UAPI_QUERY_PORT_ESW_OWNER_VHCA_ID:
> The E-Switch owner vhca id of the vport.
>
> Reviewed-by: Maor Gottlieb <maorg@nvidia.com>
> Signed-off-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
> Changelog:
> v2:
> * Changed __u64 to be __aligned_u64 in the uapi header
> v1: https://lore.kernel.org/linux-api/20210322093932.398466-1-leon@kernel.org
> * Missed sw_owner check for CX-6 device, fixed it.
> v0: https://lore.kernel.org/linux-api/20210318135221.681014-1-leon@kernel.org
> ---
> drivers/infiniband/hw/mlx5/std_types.c | 177 ++++++++++++++++++++++
> include/uapi/rdma/mlx5_user_ioctl_cmds.h | 9 ++
> include/uapi/rdma/mlx5_user_ioctl_verbs.h | 25 +++
> 3 files changed, 211 insertions(+)
Where is the rdma-core part of this? Did I miss it someplace?
Jason
next prev parent reply other threads:[~2021-04-08 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 8:50 [PATCH rdma-next v2] RDMA/mlx5: Expose private query port Leon Romanovsky
2021-04-08 18:54 ` Jason Gunthorpe [this message]
2021-04-11 11:43 ` Leon Romanovsky
2021-04-11 12:33 ` Yishai Hadas
2021-04-13 20:03 ` Jason Gunthorpe
2021-04-13 20:25 ` Mark Bloch
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=20210408185412.GA678376@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=mbloch@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).