Re: [PATCH v2 iproute2-next 0/4] Introduce FRMR pools

Stephen Hemminger
2026-04-27T18:20:30Z

On Sun, 5 Apr 2026 11:09:55 -0600
David Ahern <dsahern@gmail.com> wrote:

> On 3/30/26 11:31 AM, Chiara Meiohas wrote:
> > 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.
> >
> > These patches are complimentary to the kernel patches:
> > https://lore.kernel.org/linux-rdma/20260226-frmr_pools-v4-0-95360b54f15e@nvidia.com/
> >
>
> applied after fixing up a few nits.
>
> Please clone the ai review prompts from:
> https://github.com/masoncl/review-prompts.git
>
> Run the setup scripts and have ai review patches before sending. This
> should really be part of both kernel and iproute2 development workflow now.

I rebased UAPI headers based on 7.1-rc1 and iproute2/rdma will not build.
Looks like RDMA did not get merged in 7.1.

Will have to back it out if not going in 7.1