From: sashiko-bot@kernel.org
To: "Eric Davis" <eric.davis@broadcom.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v3 05/13] RDMA/core: extended address handle attributes
Date: Tue, 10 Nov 2026 04:45:29 +0000 [thread overview]
Message-ID: <sashiko-outbox-206235@kernel.org> (raw)
In-Reply-To: <20261109-uet-ib-core-v3-5-3e7e7ffed2e9@broadcom.com>
> From: Eric Davis <eric.davis@broadcom.com>
>
> An unconnected transport over UET resolves a peer by both its network
> address and its queue pair number. The write() create-AH command has no
> room for additional attributes. Add rdma_ah_attr_ex to carry new
> attributes, reach it through rdma_ah_init_attr, and add an ioctl method
> that supports it.
>
> rdma_create_user_ah() now takes the init attributes rather than the
> address alone, so callers pass the wider set.
>
> Signed-off-by: Eric Davis <eric.davis@broadcom.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-uet-ib-core-v3-0-3e7e7ffed2e9@broadcom.com?part=5
next prev parent reply other threads:[~2026-11-10 4:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 4:00 [PATCH rdma-next v3 00/13] RDMA/core: Ultra Ethernet transport verbs Eric Davis via B4 Relay
2026-11-10 4:00 ` [PATCH rdma-next v3 01/13] RDMA/core: widen the uverbs object key Eric Davis via B4 Relay
2026-11-10 4:10 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 02/13] RDMA/core: add the UET GID types Eric Davis via B4 Relay
2026-11-10 4:21 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 03/13] RDMA/core: report the reliable unconnected device capabilities Eric Davis via B4 Relay
2026-11-10 4:25 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 04/13] RDMA/core: add the reliable unconnected queue pair type Eric Davis via B4 Relay
2026-11-10 4:36 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 05/13] RDMA/core: extended address handle attributes Eric Davis via B4 Relay
2026-11-10 4:45 ` sashiko-bot [this message]
2026-11-10 4:00 ` [PATCH rdma-next v3 06/13] RDMA/core: query the semantics a queue pair type guarantees Eric Davis via B4 Relay
2026-11-10 4:49 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 07/13] RDMA/core: job and job key objects Eric Davis via B4 Relay
2026-11-10 4:59 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 08/13] RDMA/uverbs: factor out the queue pair attribute copy Eric Davis via B4 Relay
2026-11-10 5:04 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 09/13] RDMA/core: create a queue pair ready to send Eric Davis via B4 Relay
2026-11-10 5:14 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 10/13] RDMA/core: queue pair attributes for unconnected transports Eric Davis via B4 Relay
2026-11-10 5:29 ` sashiko-bot
2026-11-11 16:45 ` Eric Davis
2026-11-10 4:00 ` [PATCH rdma-next v3 11/13] RDMA/core: extended memory registration Eric Davis via B4 Relay
2026-11-10 5:55 ` sashiko-bot
2026-11-11 16:46 ` Eric Davis
2026-11-10 4:00 ` [PATCH rdma-next v3 12/13] RDMA/core: 64-bit memory keys Eric Davis via B4 Relay
2026-11-10 6:01 ` sashiko-bot
2026-11-10 4:00 ` [PATCH rdma-next v3 13/13] RDMA/core: attach a memory region to a queue pair Eric Davis via B4 Relay
2026-11-10 6:20 ` sashiko-bot
2026-11-11 16:49 ` Eric Davis
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=sashiko-outbox-206235@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eric.davis@broadcom.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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