From: Chiara Meiohas <cmeiohas@nvidia.com>
To: David Ahern <dsahern@gmail.com>,
leon@kernel.org, stephen@networkplumber.org
Cc: michaelgur@nvidia.com, jgg@nvidia.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next 0/4] Introduce FRMR pools
Date: Mon, 9 Mar 2026 17:48:04 +0200 [thread overview]
Message-ID: <0260a707-8fc9-4921-9adb-7295108d9f2c@nvidia.com> (raw)
In-Reply-To: <8d4e0668-9f96-44fa-bfd5-898e6f5a2827@gmail.com>
On 07/03/2026 2:16, David Ahern wrote:
> On 3/2/26 8:51 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.
>>
> reference to the kernel side patches? have those been merged?
>
yes - the kernel patches have been merged:
https://lore.kernel.org/linux-rdma/20260226-frmr_pools-v4-0-95360b54f15e@nvidia.com/
Regarding the other comments, we're looking into them and will address them soon
Thanks,
Chiara
next prev parent reply other threads:[~2026-03-09 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 15:51 [PATCH iproute2-next 0/4] Introduce FRMR pools Chiara Meiohas
2026-03-02 15:51 ` [PATCH iproute2-next 1/4] rdma: Update headers Chiara Meiohas
2026-03-02 15:51 ` [PATCH iproute2-next 2/4] rdma: Add resource FRMR pools show command Chiara Meiohas
2026-03-07 1:45 ` David Ahern
2026-03-16 17:17 ` Michael Gur
2026-03-02 15:51 ` [PATCH iproute2-next 3/4] rdma: Add FRMR pools set aging command Chiara Meiohas
2026-03-02 15:52 ` [PATCH iproute2-next 4/4] rdma: Add FRMR pools set pinned command Chiara Meiohas
2026-03-07 0:16 ` [PATCH iproute2-next 0/4] Introduce FRMR pools David Ahern
2026-03-09 15:48 ` Chiara Meiohas [this message]
2026-03-07 1:45 ` David Ahern
2026-03-16 21:37 ` Michael Gur
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=0260a707-8fc9-4921-9adb-7295108d9f2c@nvidia.com \
--to=cmeiohas@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