diff options
| author | Patrisious Haddad <[email protected]> | 2023-10-09 10:43:58 +0000 |
|---|---|---|
| committer | Leon Romanovsky <[email protected]> | 2023-10-19 06:31:00 +0000 |
| commit | 465d6b42f1a3b855c06da1d4d3b09907d261af69 (patch) | |
| tree | 77fa511b88bb84e06d0e0c5f7db4b9c07e7d4852 /scripts/gdb/vmlinux-gdb.py | |
| parent | RDMA/bnxt_re: Do not report SRQ error in srq notification (diff) | |
| download | kernel-465d6b42f1a3b855c06da1d4d3b09907d261af69.tar.gz kernel-465d6b42f1a3b855c06da1d4d3b09907d261af69.zip | |
RDMA/core: Add support to set privileged QKEY parameter
Add netlink command that enables/disables privileged QKEY by default.
It is disabled by default, since according to IB spec only privileged
users are allowed to use privileged QKEY.
According to the IB specification rel-1.6, section 3.5.3:
"QKEYs with the most significant bit set are considered controlled
QKEYs, and a HCA does not allow a consumer to arbitrarily specify a
controlled QKEY."
Using rdma tool,
$rdma system set privileged-qkey on
When enabled non-privileged users would be able to use
controlled QKEYs which are considered privileged.
Using rdma tool,
$rdma system set privileged-qkey off
When disabled only privileged users would be able to use
controlled QKEYs.
You can also use the command below to check the parameter state:
$rdma system show
netns shared privileged-qkey off copy-on-fork on
Signed-off-by: Patrisious Haddad <[email protected]>
Link: https://lore.kernel.org/r/90398be70a9d23d2aa9d0f9fd11d2c264c1be534.1696848201.git.leon@kernel.org
Signed-off-by: Leon Romanovsky <[email protected]>
Diffstat (limited to 'scripts/gdb/vmlinux-gdb.py')
0 files changed, 0 insertions, 0 deletions
