From: Patrisious Haddad <phaddad@nvidia.com>
To: <jgg@ziepe.ca>, <leon@kernel.org>, <dsahern@gmail.com>,
<stephen@networkplumber.org>
Cc: Patrisious Haddad <phaddad@nvidia.com>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>, <huangjunxian6@hisilicon.com>,
<michaelgur@nvidia.com>
Subject: [PATCH v2 iproute2-next 0/3] Add support to set privileged qkey parameter
Date: Mon, 23 Oct 2023 14:22:14 +0300 [thread overview]
Message-ID: <20231023112217.3439-1-phaddad@nvidia.com> (raw)
This patchset adds support to enable or disable privileged QKEY.
When enabled, non-privileged users will be allowed to specify a controlled QKEY.
The corresponding kernel commit is yet to be merged so currently there
is no hash but the commit name is
("RDMA/core: Add support to set privileged qkey parameter")
All the information regarding the added parameter and its usage are included
in the commits below and the edited man page.
---
v1->v2:
- Uses print_color_on_off instead of print_color_string for printing.
- Uses parse_on_off instead of manual parsing.
Patrisious Haddad (3):
rdma: update uapi headers
rdma: Add an option to set privileged QKEY parameter
rdma: Adjust man page for rdma system set privileged_qkey command
man/man8/rdma-system.8 | 32 ++++++++++++++++---
rdma/include/uapi/rdma/rdma_netlink.h | 6 ++++
rdma/sys.c | 46 +++++++++++++++++++++++++--
rdma/utils.c | 1 +
4 files changed, 78 insertions(+), 7 deletions(-)
--
2.18.1
next reply other threads:[~2023-10-23 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:22 Patrisious Haddad [this message]
2023-10-23 11:22 ` [PATCH v2 iproute2-next 1/3] rdma: update uapi headers Patrisious Haddad
2023-10-23 11:22 ` [PATCH v2 iproute2-next 2/3] rdma: Add an option to set privileged QKEY parameter Patrisious Haddad
2023-10-24 15:34 ` Petr Machata
2023-10-24 17:02 ` David Ahern
2023-10-25 6:26 ` Patrisious Haddad
2023-10-25 8:34 ` Petr Machata
2023-10-25 8:25 ` Petr Machata
2023-10-23 11:22 ` [PATCH v2 iproute2-next 3/3] rdma: Adjust man page for rdma system set privileged_qkey command Patrisious Haddad
2023-10-24 16:09 ` Petr Machata
2023-10-24 17:04 ` David Ahern
2023-10-25 6:10 ` Patrisious Haddad
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=20231023112217.3439-1-phaddad@nvidia.com \
--to=phaddad@nvidia.com \
--cc=dsahern@gmail.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=michaelgur@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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