RDMA-SYSTEM(8)
๐ RDMA-SYSTEM(8) โ the rdma-system girlies' guide ๐
okay so bestie, welcome to the RDMA-SYSTEM(8) manual page, she's a Linux one, and she's literally all about RDMA subsystem configuration ๐ no cap.
โจ NAME โจ
rdma-system โ RDMA subsystem configuration. that's it, that's the whole vibe ๐ฆ
๐ธ SYNOPSIS ๐ธ
rdma [ OPTIONS ] sys { COMMAND | help }
OPTIONS := { -V[ersion] | -d[etails] }
rdma system show
rdma system set netns NEWMODE
rdma system set privileged-qkey NEWSTATE
rdma system help
๐ DESCRIPTION ๐
๐
rdma system set โ set RDMA subsystem network namespace mode or privileged qkey mode
๐ rdma system show โ display RDMA subsystem network namespace mode, privileged qkey state and whether RDMA monitoring is supported
okay so now the details, because this is the part where you actually need to pay attention, bestie ๐ซถ
NEWMODE โ this one specifies the RDMA subsystem mode. it's either exclusive or shared. when a user wants to assign a dedicated RDMA device to a particular network namespace, exclusive mode should be set before creating any network namespace. and here's the tea โ: if there are active network namespaces and if one or more RDMA devices exist, changing mode from shared to exclusive returns error code EBUSY. so yeah, that's gonna fail on you, plan accordingly ๐ญ
when the RDMA subsystem is in shared mode, the RDMA device is accessible in all network namespaces. so when you don't need RDMA device isolation among multiple network namespaces, shared mode can be used. it's giving "we all share, we're all besties" energy โจ
it is preferred to not change the subsystem mode when there is active RDMA traffic running, even though it is supported. like, you can, but... girl. don't. ๐
NEWSTATE โ specifies the new state of the privileged-qkey parameter, either on or off. this parameter determines whether a non-privileged user is allowed to specify a controlled QKEY or not. periodt. ๐
๐ฅ EXAMPLES ๐ฅ
rdma system showshows the state of RDMA subsystem network namespace mode on the system, the state of theprivileged qkeyparameter and whether RDMA monitor is supported. the whole status check, one command, iconic โญrdma system set netns exclusivesets the RDMA subsystem in network namespace exclusive mode. in this mode RDMA devices are visible only in single network namespace. it's giving main character only, no sharing ๐rdma system set netns sharedsets the RDMA subsystem in network namespace shared mode. in this mode RDMA devices are shared among network namespaces. communal slay ๐rdma system set privileged-qkey onsets theprivileged-qkeyparameter to on. in this state non-privileged user is allowed to specify a controlled QKEY ๐rdma system set privileged-qkey offsets theprivileged-qkeyparameter to off. in this state non-privileged user is not allowed to specify a controlled QKEY. sorry babe, locked down ๐
๐ SEE ALSO ๐
rdma(8), rdma-link(8), rdma-resource(8), rdma-monitor(8), network_namespaces(7), namespaces(7), โ go read those next, bestie, they're all part of the same little friend group ๐ง
๐ AUTHOR ๐
Parav Pandit <parav@mellanox.com> โ thank you for your service, king ๐ซก
and that's the whole page, bestie!! this one came from iproute2, dated 06 Jul 2017, and it lives in the RDMA-SYSTEM(8) section of the manual. go forth and configure those RDMA subsystems responsibly, mwah ๐๐ธ
๐ฆ where this page comes from
- alpine 3.24: iproute2-doc 7.0.0-r0 ยท GPL-2.0-or-later
- arch rolling: iproute2 7.2.0-1
- arch rolling: iproute2 7.3.0-1 ยท GPL-2.0-or-later
- centos-stream 10: iproute 7.0.0-2.el10 ยท GPL-2.0-or-later AND NIST-PD
- nixos 26.05: iproute2 7.0.0
- nixpkgs unstable: iproute2 7.2.0
- ubuntu stonking: iproute2 7.2.0-1ubuntu1 ยท GPL-2.0-only
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms