From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Doug Ledford <doug.ledford@hpe.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Slingshot Open Source Team
<slingshot-os-team@groups.ext.hpe.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Iraimani P <iraimani.pavadai@hpe.com>,
Mamila Santosh <santosh-kumar.mamila@hpe.com>
Subject: Re: [PATCH 04/11] RDMA/cxi: add the native ABI and resource definitions
Date: Thu, 5 Nov 2026 14:54:17 +0100 [thread overview]
Message-ID: <auyIsEVLUBT4i12F@monoceros> (raw)
In-Reply-To: <20261030-cxi-for-next-v1-4-bc6e49e07037@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
On Fri, Oct 30, 2026 at 09:35:32PM -0700, Doug Ledford wrote:
> +#include <linux/mod_devicetable.h>
Please drop this include. Even if there was a usage of a *_device_id
this would be wrong.
> [...]
> +struct cxiverbs_lni *cxiverbs_lni_get(struct cxiverbs_ucontext *ctx,
> + u32 handle);
unusual indention, please align the continuation line to the opening (.
I would expect that this declaration is added in the same commit as the
actual function.
> +void cxiverbs_lni_put(struct cxiverbs_lni *lni);
> +
> +/* -----------------------------------------------------------------------
> + * Protection domain (ib_pd) → shared JobID-anchored LNI + RGID (isolation)
> + *
> + * PD no longer owns its own LNI; instead it references the JobID-anchored LNI
> + * from the ucontext. The PD can optionally express a preferred_svc_id for QPs;
> + * if not set, QPs can select any service at creation.
> + * -----------------------------------------------------------------------
> + */
> +struct cxiverbs_pd {
> + struct ib_pd ibpd;
> + struct cxiverbs_lni *lni_ref;
> + struct xarray qpns;
> +
> + u32 job_id; /* cached from ucontext->job_id */
> + u32 preferred_svc_id; /* optional service preference (0 = any) */
> +
> + u32 rgid; /* RGID for resource isolation */
> + u32 pd_id; /* RGID-based PD identifier */
> + u32 default_pidonfep;
> + u32 pidonfep;
> + u32 qpn_addr_mode;
> + bool default_pidonfep_valid;
> + bool pidonfep_valid;
> + struct mutex resource_lock;
> +};
Please make the alignment here consistent. Either align all members or
none, but not this mixture. My preference would be a single space
because these alignments tend to get annoying when they are kept during
future changes or diverge even more. Same for a few further struct
definitions further down this file.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-11-05 13:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 4:35 [PATCH 00/11] Subject: [PATCH for-next 00/11] RDMA/cxi: add the HPE Cassini verbs driver Doug Ledford
2026-10-31 4:35 ` [PATCH 01/11] RDMA/core: read selected counters with timestamps Doug Ledford
2026-10-31 4:35 ` [PATCH 02/11] RDMA/core: allow jobs without an address table Doug Ledford
2026-10-31 4:35 ` [PATCH 03/11] RDMA/core: add Slingshot identifiers and driver-owned GIDs Doug Ledford
2026-10-31 4:35 ` [PATCH 04/11] RDMA/cxi: add the native ABI and resource definitions Doug Ledford
2026-11-05 13:54 ` Uwe Kleine-König [this message]
2026-10-31 4:35 ` [PATCH 05/11] RDMA/cxi: add the auxiliary device and driver ops Doug Ledford
2026-10-31 4:35 ` [PATCH 06/11] RDMA/cxi: add explicit context LNI and PID lifetimes Doug Ledford
2026-10-31 4:35 ` [PATCH 07/11] RDMA/cxi: add VNI-isolated queue pairs Doug Ledford
2026-10-31 4:35 ` [PATCH 08/11] RDMA/cxi: add native memory registration Doug Ledford
2026-10-31 4:35 ` [PATCH 09/11] RDMA/cxi: add services jobs profiles queues and counting triggers Doug Ledford
2026-10-31 4:35 ` [PATCH 10/11] RDMA/cxi: read the NIC telemetry through counters Doug Ledford
2026-10-31 4:35 ` [PATCH 11/11] RDMA/cxi: wire the driver into the build Doug Ledford
2026-11-03 14:28 ` [PATCH 00/11] Subject: [PATCH for-next 00/11] RDMA/cxi: add the HPE Cassini verbs driver Leon Romanovsky
2026-11-03 14:30 ` Jason Gunthorpe
2026-11-04 9:54 ` Leon Romanovsky
2026-11-04 16:17 ` Doug Ledford
2026-11-04 16:14 ` Doug Ledford
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=auyIsEVLUBT4i12F@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=doug.ledford@hpe.com \
--cc=iraimani.pavadai@hpe.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=santosh-kumar.mamila@hpe.com \
--cc=slingshot-os-team@groups.ext.hpe.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.