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 v1] RDMA/mlx5: Expose private query port
Date: Mon, 29 Mar 2021 15:35:19 -0300 [thread overview]
Message-ID: <20210329183519.GA1230305@nvidia.com> (raw)
In-Reply-To: <20210322093932.398466-1-leon@kernel.org>
On Mon, Mar 22, 2021 at 11:39:32AM +0200, Leon Romanovsky wrote:
> +struct mlx5_ib_uapi_query_port {
> + __u64 flags;
> + __u16 vport;
> + __u16 vport_vhca_id;
> + __u16 esw_owner_vhca_id;
> + __u16 rsvd0;
> + __u64 vport_steering_icm_rx;
> + __u64 vport_steering_icm_tx;
__aligned_u64 for all uapi structures
Jason
prev parent reply other threads:[~2021-03-29 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 9:39 [PATCH rdma-next v1] RDMA/mlx5: Expose private query port Leon Romanovsky
2021-03-29 18:35 ` Jason Gunthorpe [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=20210329183519.GA1230305@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).