public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	linux-rdma@vger.kernel.org, Mark Zhang <markzhang@nvidia.com>,
	Or Har-Toov <ohartoov@nvidia.com>,
	Vlad Dumitrescu <vdumitrescu@nvidia.com>
Subject: [PATCH rdma-next 0/5] IB service resolution
Date: Mon, 30 Jun 2025 13:52:30 +0300	[thread overview]
Message-ID: <cover.1751279793.git.leonro@nvidia.com> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

From Mark,

This patchset adds support to resolve IB service records from SM. With
this feature, the user-space is able to resolve and query IB address
information like DGID and PKEY based on an IB service name or ID,
through new ucma commands.

New CM states:
 * RDMA_CM_ADDRINFO_QUERY - Indicates cm is in the process of IB service
   resolution;
 * RDMA_CM_ADDRINFO_RESOLVED - Indicates cm has finished the process of
   IB service resolution.

New CM events:
 * RDMA_CM_EVENT_ADDRINFO_RESOLVED - Indicates successful resolution of
   address information.
 * RDMA_CM_EVENT_ADDRINFO_ERROR - Indicates a failure in address
   information resolution.

The patchset also enables writing custom events into the CM. This is
particularly useful for applications that require events not typically
generated in the standard rdmacm flow. Two new event types are
supported:

 * RDMA_CM_EVENT_USER - A user-defined event, where the event details
   are specified by the application and not interpreted by the librdmacm
   library.
 * RDMA_CM_EVENT_INTERNAL - An internal event, used and consumed exclusively
   by the librdmacm library.

For instance, the new user-space API rdma_resolve_addrinfo() will
support both SA (Service Agent) and DNS resolution. In the DNS case,
since there is no standard CM event generated upon completion, an
RDMA_CM_EVENT_INTERNAL event with "ADDRINFO_RESOLVED" information as the
parameter can be written into the CM. This allows the librdmacm library
to receive the event and report an ADDRINFO_RESOLVED event to the user,
ensuring that DNS resolution follows the same workflow as IB service
record resolution.

Thanks

Mark Zhang (5):
  RDMA/sa_query: Add RMPP support for SA queries
  RDMA/sa_query: Support IB service records resolution
  RDMA/cma: Support IB service record resolution
  RDMA/ucma: Support query resolved service records
  RDMA/ucma: Support write an event into a CM

 drivers/infiniband/core/cma.c      | 136 +++++++++++++-
 drivers/infiniband/core/cma_priv.h |   4 +-
 drivers/infiniband/core/sa_query.c | 277 +++++++++++++++++++++++++++--
 drivers/infiniband/core/ucma.c     | 120 ++++++++++++-
 include/rdma/ib_mad.h              |   1 +
 include/rdma/ib_sa.h               |  37 ++++
 include/rdma/rdma_cm.h             |  21 ++-
 include/uapi/rdma/ib_user_sa.h     |  14 ++
 include/uapi/rdma/rdma_user_cm.h   |  42 ++++-
 9 files changed, 634 insertions(+), 18 deletions(-)

-- 
2.50.0


             reply	other threads:[~2025-06-30 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30 10:52 Leon Romanovsky [this message]
2025-06-30 10:52 ` [PATCH rdma-next 1/5] RDMA/sa_query: Add RMPP support for SA queries Leon Romanovsky
2025-06-30 10:52 ` [PATCH rdma-next 2/5] RDMA/sa_query: Support IB service records resolution Leon Romanovsky
2025-06-30 10:52 ` [PATCH rdma-next 3/5] RDMA/cma: Support IB service record resolution Leon Romanovsky
2025-06-30 10:52 ` [PATCH rdma-next 4/5] RDMA/ucma: Support query resolved service records Leon Romanovsky
2025-06-30 10:52 ` [PATCH rdma-next 5/5] RDMA/ucma: Support write an event into a CM Leon Romanovsky
2025-08-13 10:16 ` [PATCH rdma-next 0/5] IB service resolution Leon Romanovsky

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=cover.1751279793.git.leonro@nvidia.com \
    --to=leon@kernel.org \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@nvidia.com \
    --cc=ohartoov@nvidia.com \
    --cc=vdumitrescu@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox