From: Chiara Meiohas <cmeiohas@nvidia.com>
To: David Ahern <dsahern@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: leon@kernel.org, michaelgur@nvidia.com, jgg@nvidia.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Patrisious Haddad <phaddad@nvidia.com>
Subject: Re: [PATCH v2 iproute2-next 1/4] rdma: Update headers
Date: Tue, 28 Apr 2026 13:05:49 +0300 [thread overview]
Message-ID: <98c17c60-6747-4c2b-bfe4-ce9bbe560f6d@nvidia.com> (raw)
In-Reply-To: <77e1a762-e204-497b-b7cb-40d5a93f8ec7@gmail.com>
On 27/04/2026 21:27, David Ahern wrote:
> On 4/27/26 12:25 PM, Stephen Hemminger wrote:
>> On Mon, 30 Mar 2026 20:31:15 +0300
>> Chiara Meiohas <cmeiohas@nvidia.com> wrote:
>>
>>> From: Michael Guralnik <michaelgur@nvidia.com>
>>>
>>> Update rdma_netlink.h file up to kernel commit dbd0472fd7a5
>>> ("RDMA/nldev: Expose kernel-internal FRMR pools in netlink")
>>>
>>> Signed-off-by: Michael Guralnik <michaelgur@nvidia.com>
>>> Reviewed-by: Patrisious Haddad <phaddad@nvidia.com>
>>> Reviewed-by: Chiara Meiohas <cmeiohas@nvidia.com>
>> The upstream macro names changed, the iproute2 build is broken after
>> current headers sync.
>>
>> In file included from res.c:7:
>> res.h: In function ‘_res_frmr_pools’:
>> res.h:203:26: error: ‘RDMA_NLDEV_CMD_RES_FRMR_POOLS_GET’ undeclared (first use in this function); did you mean ‘RDMA_NLDEV_CMD_FRMR_POOLS_GET’?
>> 203 | RES_FUNC(res_frmr_pools, RDMA_NLDEV_CMD_RES_FRMR_POOLS_GET,
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> res.h:56:44: note: in definition of macro ‘RES_FUNC’
>> 56 | _command = res_get_command(command, rd); \
>> | ^~~~~~~
>> res.h:203:26: note: each undeclared identifier is reported only once for each function it appears in
>> 203 | RES_FUNC(res_frmr_pools, RDMA_NLDEV_CMD_RES_FRMR_POOLS_GET,
>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> res.h:56:44: note: in definition of macro ‘RES_FUNC’
>> 56 | _command = res_get_command(command, rd); \
>> | ^~~~~~~
>
> Looks like the merged API does not have the _RES part of the uapi:
>
> kernel vs iproute2:
>
> @@ -590,19 +590,19 @@
> /*
> * FRMR Pools attributes
> */
> - RDMA_NLDEV_ATTR_FRMR_POOLS, /* nested table */
> - RDMA_NLDEV_ATTR_FRMR_POOL_ENTRY, /* nested table */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY, /* nested table */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY_ATS, /* u8 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY_ACCESS_FLAGS, /* u32 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY_VENDOR_KEY, /* u64 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY_NUM_DMA_BLOCKS, /* u64 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_QUEUE_HANDLES, /* u32 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_MAX_IN_USE, /* u64 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_IN_USE, /* u64 */
> - RDMA_NLDEV_ATTR_FRMR_POOLS_AGING_PERIOD, /* u32 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_PINNED_HANDLES, /* u32 */
> - RDMA_NLDEV_ATTR_FRMR_POOL_KEY_KERNEL_VENDOR_KEY, /* u64 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOLS, /* nested table */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_ENTRY, /* nested table */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY, /* nested table */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY_ATS, /* u8 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY_ACCESS_FLAGS, /* u32 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY_VENDOR_KEY, /* u64 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY_NUM_DMA_BLOCKS, /* u64 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_QUEUE_HANDLES, /* u32 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_MAX_IN_USE, /* u64 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_IN_USE, /* u64 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_AGING_PERIOD, /* u32 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_PINNED, /* u32 */
> + RDMA_NLDEV_ATTR_RES_FRMR_POOL_KEY_KERNEL_VENDOR_KEY, /* u64 */
>
> /*
Thanks for catching this.
We will prepare a sync patch to align the names with the kernel and send it shortly.
Best regards,
Chiara
next prev parent reply other threads:[~2026-04-28 10:06 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 [this message]
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
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=98c17c60-6747-4c2b-bfe4-ce9bbe560f6d@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=phaddad@nvidia.com \
--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