From: Patrisious Haddad <phaddad@nvidia.com>
To: <leon@kernel.org>, <dsahern@gmail.com>, <stephen@networkplumber.org>
Cc: Patrisious Haddad <phaddad@nvidia.com>, <netdev@vger.kernel.org>,
<jgg@nvidia.com>, <michaelgur@nvidia.com>,
<linux-rdma@vger.kernel.org>
Subject: [RFC iproute2-next 0/4] Introduce FRMR pools
Date: Mon, 22 Dec 2025 15:25:42 +0200 [thread overview]
Message-ID: <20251222132549.995921-1-phaddad@nvidia.com> (raw)
From Michael:
This series adds support for managing Fast Registration Memory Region
(FRMR) pools in rdma tool, enabling users to monitor and configure FRMR
pool behavior.
FRMR pools are used to cache and reuse Fast Registration Memory Region
handles to improve performance by avoiding the overhead of repeated
memory region creation and destruction. This series introduces commands
to view FRMR pool statistics and configure pool parameters such as
aging time and pinned handle count.
The 'show' command allows users to display FRMR pools created on
devices, their properties, and usage statistics. Each pool is identified
by a unique key (hex-encoded properties) for easy reference in
subsequent operations.
The aging 'set' command allows users to modify the aging time parameter,
which controls how long unused FRMR handles remain in the pool before
being released.
The pinned 'set' command allows users to configure the number of pinned
handles in a pool. Pinned handles are exempt from aging and remain
permanently available for reuse, which is useful for workloads with
predictable memory region usage patterns.
Command usage and examples are included in the commits and man pages.
Michael Guralnik (4):
rdma: Update headers
rdma: Add resource FRMR pools show command
rdma: Add FRMR pools set aging command
rdma: Add FRMR pools set pinned command
man/man8/rdma-resource.8 | 51 +++-
rdma/Makefile | 2 +-
rdma/include/uapi/rdma/rdma_netlink.h | 22 ++
rdma/res-frmr-pools.c | 342 ++++++++++++++++++++++++++
rdma/res.c | 19 +-
rdma/res.h | 20 ++
6 files changed, 453 insertions(+), 3 deletions(-)
create mode 100644 rdma/res-frmr-pools.c
--
2.47.0
next reply other threads:[~2025-12-22 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 13:25 Patrisious Haddad [this message]
2025-12-22 13:25 ` [RFC iproute2-next 1/4] rdma: Update headers Patrisious Haddad
2025-12-22 13:25 ` [RFC iproute2-next 2/4] rdma: Add resource FRMR pools show command Patrisious Haddad
2025-12-22 13:25 ` [RFC iproute2-next 3/4] rdma: Add FRMR pools set aging command Patrisious Haddad
2025-12-22 13:25 ` [RFC iproute2-next 4/4] rdma: Add FRMR pools set pinned command 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=20251222132549.995921-1-phaddad@nvidia.com \
--to=phaddad@nvidia.com \
--cc=dsahern@gmail.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).