From: David Ahern <dsahern@gmail.com>
To: Chiara Meiohas <cmeiohas@nvidia.com>,
leon@kernel.org, stephen@networkplumber.org
Cc: michaelgur@nvidia.com, jgg@nvidia.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Patrisious Haddad <phaddad@nvidia.com>
Subject: Re: [PATCH iproute2-next 2/4] rdma: Add resource FRMR pools show command
Date: Fri, 6 Mar 2026 18:45:49 -0700 [thread overview]
Message-ID: <d8e79d96-3dfd-4008-85a3-f2cb1da2845c@gmail.com> (raw)
In-Reply-To: <20260302155200.2611098-3-cmeiohas@nvidia.com>
On 3/2/26 8:51 AM, Chiara Meiohas wrote:
> diff --git a/rdma/res-frmr-pools.c b/rdma/res-frmr-pools.c
> new file mode 100644
> index 00000000..97d59705
> --- /dev/null
> +++ b/rdma/res-frmr-pools.c
> @@ -0,0 +1,190 @@
> +// SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
> +/*
> + * res-frmr-pools.c RDMA tool
> + * Authors: Michael Guralnik <michaelgur@nvidia.com>
> + */
> +
> +#include "res.h"
> +#include <inttypes.h>
> +
> +#define FRMR_POOL_KEY_SIZE 21
> +#define FRMR_POOL_KEY_HEX_SIZE (FRMR_POOL_KEY_SIZE * 2)
> +union frmr_pool_key {
> + struct {
> + uint8_t ats;
> + uint32_t access_flags;
> + uint64_t vendor_key;
> + uint64_t num_dma_blocks;
> + } __attribute__((packed)) fields;
why is packed needed on this struct? why can't the fields be re-arranged
to not require it and just let the extra 3B be at the end unused?
> + uint8_t raw[FRMR_POOL_KEY_SIZE];
> +};
> +
next prev parent reply other threads:[~2026-03-07 1:45 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 [this message]
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
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=d8e79d96-3dfd-4008-85a3-f2cb1da2845c@gmail.com \
--to=dsahern@gmail.com \
--cc=cmeiohas@nvidia.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