public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@gmail.com>,
	Chiara Meiohas <cmeiohas@nvidia.com>,
	leon@kernel.org, michaelgur@nvidia.com,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 iproute2-next 0/4] Introduce FRMR pools
Date: Mon, 27 Apr 2026 15:22:23 -0300	[thread overview]
Message-ID: <20260427182223.GB718365@nvidia.com> (raw)
In-Reply-To: <20260427112025.49ebbd73@phoenix.local>

On Mon, Apr 27, 2026 at 11:20:25AM -0700, Stephen Hemminger wrote:
> 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

I see it here:

commit dbd0472fd7a5bdd0b86c21c36f8afa713baa7653
Author: Michael Guralnik <michaelgur@nvidia.com>
Date:   Thu Feb 26 15:52:16 2026 +0200

    RDMA/nldev: Expose kernel-internal FRMR pools in netlink
    
    Allow netlink users, through the usage of driver-details netlink
    attribute, to get information about internal FRMR pools that use the
    kernel_vendor_key FRMR key member.
    
    Signed-off-by: Michael Guralnik <michaelgur@nvidia.com>
    Reviewed-by: Patrisious Haddad <phaddad@nvidia.com>
    Signed-off-by: Edward Srouji <edwards@nvidia.com>
    Link: https://patch.msgid.link/20260226-frmr_pools-v4-11-95360b54f15e@nvidia.com
    Signed-off-by: Leon Romanovsky <leon@kernel.org>

Did some part get missed?

Jason

  reply	other threads:[~2026-04-27 18:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 17:31 [PATCH v2 iproute2-next 0/4] Introduce FRMR pools Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 1/4] rdma: Update headers Chiara Meiohas
2026-04-27 18:25   ` Stephen Hemminger
2026-04-27 18:27     ` David Ahern
2026-04-28 10:05       ` Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 2/4] rdma: Add resource FRMR pools show command Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 3/4] rdma: Add FRMR pools set aging command Chiara Meiohas
2026-03-30 17:31 ` [PATCH v2 iproute2-next 4/4] rdma: Add FRMR pools set pinned command Chiara Meiohas
2026-04-05 17:09 ` [PATCH v2 iproute2-next 0/4] Introduce FRMR pools David Ahern
2026-04-05 17:44   ` Chiara Meiohas
2026-04-27 18:20   ` Stephen Hemminger
2026-04-27 18:22     ` Jason Gunthorpe [this message]
2026-04-05 17:10 ` patchwork-bot+netdevbpf

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=20260427182223.GB718365@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=cmeiohas@nvidia.com \
    --cc=dsahern@gmail.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