From: Tao Cui <cui.tao@linux.dev>
To: dsahern@kernel.org, leonro@nvidia.com
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
cui.tao@linux.dev, cuitao@kylinos.cn
Subject: [PATCH iproute2-next v5 0/2] rdma: display resource limits in curr/max format
Date: Fri, 10 Jul 2026 09:17:57 +0800 [thread overview]
Message-ID: <20260710011759.378893-1-cui.tao@linux.dev> (raw)
From: Tao Cui <cuitao@kylinos.cn>
This series adds support for displaying RDMA device resource limits in
curr/max format in the rdma tool, building on the kernel uapi attribute
RDMA_NLDEV_ATTR_RES_SUMMARY_ENTRY_MAX which has landed in linux-next
(kernel commit 5911f6d6e7ce [1]).
Patch 1 syncs the rdma_netlink.h uapi header from the kernel.
Patch 2 updates the rdma tool to parse the new attribute and display
resource usage in curr/max format:
$ rdma resource show
0: mlx5_0: qp 123/131072 cq 45/65536 mr 200/1000000 pd 10/32768
[1]:
Link: https://lore.kernel.org/all/20260615003646.168704-1-cui.tao@linux.dev/
Tao Cui (2):
rdma: update uapi headers
rdma: display resource limits in curr/max format
rdma/include/uapi/rdma/rdma_netlink.h | 5 +++++
rdma/res.c | 21 ++++++++++++++++++++-
rdma/utils.c | 1 +
3 files changed, 26 insertions(+), 1 deletion(-)
---
Changes in v5:
- Split the rdma_netlink.h update into its own commit following the
uapi headers sync format ("rdma: update uapi headers").
Changes in v4:
- Add a Link: reference to the kernel patch; re-send now that the
kernel side has landed in linux-next.
--
2.43.0
next reply other threads:[~2026-07-10 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 1:17 Tao Cui [this message]
2026-07-10 1:17 ` [PATCH iproute2-next v5 1/2] rdma: update uapi headers Tao Cui
2026-07-10 1:17 ` [PATCH iproute2-next v5 2/2] rdma: display resource limits in curr/max format Tao Cui
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=20260710011759.378893-1-cui.tao@linux.dev \
--to=cui.tao@linux.dev \
--cc=cuitao@kylinos.cn \
--cc=dsahern@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.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