RDMA-DEV(8)
๐ rdma-dev โ RDMA device configuration ๐
okay bestie, so this is rdma-dev, section 8 of the Linux manual pages ๐งโจ โ it's the part of the rdma command that handles all your RDMA devices. renaming them, yeeting them into namespaces, adding baby devices, deleting them. the whole glow-up. ๐
๐ธ SYNOPSIS ๐ธ
rdma [ OPTIONS ] dev { COMMAND | help }
OPTIONS := { -V[ersion] | -d[etails] }
rdma dev show [ DEV ]
rdma dev set [ DEV ] name NEWNAME
rdma dev set [ DEV ] netns {NSNAME|PID}
rdma dev set [ DEV ] adaptive-moderation [on/off]
rdma dev add [ NAME ] type [ TYPE ] parent [ PARENT_DEV ]
rdma dev delete [ NAME ]
rdma dev help
โจ DESCRIPTION โจ
๐ rdma dev set โ rename an RDMA device, or set its network namespace, or set RDMA device adaptive-moderation
that's the whole vibe. three jobs, one command, main character energy ๐
๐ rdma dev show โ display RDMA device attributes
DEVโ tells you which RDMA device to show. if you just... don't pass it? then every single device gets listed. no filter, no crumbs, all of them. ๐ซถ
๐ rdma dev add โ add a RDMA device
so you're adding a RDMA device with a specific type and a parent IB device. this new device lowkey only provides a subset of the functionalities defined in the IBTA spec โ it's not the whole package, it's the curated edit. ๐ฆ
๐ rdma dev delete โ delete a RDMA device
deletes a RDMA device that you created earlier with the add command. no take-backs unless you add it again, bestie. ๐ญ
NAMEโ the name of the device being added/deleted.TYPEโ the type of the device being added. it specifies which functionalities it provides. supported device type is:SMIโ a device with this type provides the SMI (QP0) interface. this device and its parent associate with the same HCA port and share the physical link, so when the parent doesn't support SMI, then this type of device can be created to allow the subnet manager to configure the link. literally the fixer of the family. ๐ฅ
PARENT_DEVโ the name of its parent IB device.
๐ EXAMPLES ๐
rdma dev
shows the state of all RDMA devices on the system. the full roster. โญ
rdma dev show mlx5_3
shows the state of the specified RDMA device. just the one, the chosen one. ๐
rdma dev set mlx5_3 name rdma_0
renames the mlx5_3 device to rdma_0. glow-up complete ๐
rdma dev set mlx5_3 netns foo rdma dev set mlx5_3 netns 1234
changes the network namespace of RDMA device to foo, where foo was previously created using the iproute2 ip command. (and yes, 1234 is the PID flavor of the same thing ๐ซถ)
rdma dev set mlx5_3 adaptive-moderation [on/off]
sets the state of adaptive interrupt moderation for the RDMA device. heads up: this is a global setting for the RDMA device, but the value is printed for each CQ individually, because the state is constant from CQ allocation. so like, one setting, many receipts. ๐ง
rdma dev add smi1 type SMI parent ibp8s0f1
adds a new IB device with name "smi1", type "SMI", and "ibp8s0f1" as its parent device. it's giving nepo baby but make it networking ๐
rdma dev delete smi1
deletes the IB device "smi1". gone. not me crying over smi1 ๐ญ
๐ SEE ALSO ๐
ip(8), rdma(8), rdma-link(8), rdma-resource(8), rdma-system(8), rdma-statistic(8)
๐ AUTHOR ๐
- Leon Romanovsky
<leonro@mellanox.com> - Mark Zhang
<markzhang@nvidia.com>
and that's the whole page, bestie!! ๐ written for iproute2, dated 06 Jul 2017 โ so yeah it's a lil vintage but she still ate ๐โจ mwah, go configure some devices ๐ฆ
๐ฆ where this page comes from
- arch rolling: iproute2 7.2.0-1
- arch rolling: iproute2 7.3.0-1 ยท GPL-2.0-or-later
- 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