Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Md Haris Iqbal <haris.iqbal@ionos.com>
To: linux-block@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk,
	bvanassche@acm.org, hch@lst.de, jgg@ziepe.ca, leon@kernel.org,
	jinpu.wang@ionos.com, Md Haris Iqbal <haris.iqbal@ionos.com>,
	Jia Li <jia.li@ionos.com>
Subject: [PATCH 07/13] RDMA/rmr: include client and server modules into kernel compilation
Date: Tue,  5 May 2026 09:46:19 +0200	[thread overview]
Message-ID: <20260505074644.195453-8-haris.iqbal@ionos.com> (raw)
In-Reply-To: <20260505074644.195453-1-haris.iqbal@ionos.com>

Add the per-directory Kconfig and Makefile, and wire them into the
parent drivers/infiniband Kconfig and drivers/infiniband/ulp Makefile
so RMR can be enabled in a kernel build.

Three Kconfig symbols are introduced:

  CONFIG_INFINIBAND_RMR		(silent, selected by either side)
  CONFIG_INFINIBAND_RMR_CLIENT	(depends on INFINIBAND_RTRS_CLIENT)
  CONFIG_INFINIBAND_RMR_SERVER	(depends on INFINIBAND_RTRS_SERVER)

The Makefile builds two modules: rmr-client.ko and rmr-server.ko,
sharing the pool, map, request and library code added earlier in
this series.

Signed-off-by: Md Haris Iqbal <haris.iqbal@ionos.com>
Signed-off-by: Jia Li <jia.li@ionos.com>
---
 drivers/infiniband/Kconfig          |  1 +
 drivers/infiniband/ulp/Makefile     |  1 +
 drivers/infiniband/ulp/rmr/Kconfig  | 35 +++++++++++++++++++++++++++++
 drivers/infiniband/ulp/rmr/Makefile | 23 +++++++++++++++++++
 4 files changed, 60 insertions(+)
 create mode 100644 drivers/infiniband/ulp/rmr/Kconfig
 create mode 100644 drivers/infiniband/ulp/rmr/Makefile

diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig
index a7e3f29dc037..4b2470b5a592 100644
--- a/drivers/infiniband/Kconfig
+++ b/drivers/infiniband/Kconfig
@@ -110,5 +110,6 @@ source "drivers/infiniband/ulp/srpt/Kconfig"
 source "drivers/infiniband/ulp/iser/Kconfig"
 source "drivers/infiniband/ulp/isert/Kconfig"
 source "drivers/infiniband/ulp/rtrs/Kconfig"
+source "drivers/infiniband/ulp/rmr/Kconfig"
 
 endif # INFINIBAND
diff --git a/drivers/infiniband/ulp/Makefile b/drivers/infiniband/ulp/Makefile
index 51b0d41699b8..24c8e4b00065 100644
--- a/drivers/infiniband/ulp/Makefile
+++ b/drivers/infiniband/ulp/Makefile
@@ -5,3 +5,4 @@ obj-$(CONFIG_INFINIBAND_SRPT)		+= srpt/
 obj-$(CONFIG_INFINIBAND_ISER)		+= iser/
 obj-$(CONFIG_INFINIBAND_ISERT)		+= isert/
 obj-$(CONFIG_INFINIBAND_RTRS)		+= rtrs/
+obj-$(CONFIG_INFINIBAND_RMR)		+= rmr/
diff --git a/drivers/infiniband/ulp/rmr/Kconfig b/drivers/infiniband/ulp/rmr/Kconfig
new file mode 100644
index 000000000000..1d62322a02be
--- /dev/null
+++ b/drivers/infiniband/ulp/rmr/Kconfig
@@ -0,0 +1,35 @@
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+config INFINIBAND_RMR
+	tristate
+	depends on INFINIBAND_ADDR_TRANS
+
+config INFINIBAND_RMR_CLIENT
+	tristate "RMR client module"
+	depends on INFINIBAND_ADDR_TRANS
+	depends on INFINIBAND_RTRS_CLIENT
+	select INFINIBAND_RMR
+	help
+	  Reliable Multicast over RTRS (RMR) client module.
+
+	  RMR is an RDMA ULP that provides active-active block-level
+	  replication on top of the RTRS transport.  It guarantees
+	  delivery of an I/O to a group of storage nodes and handles
+	  resynchronization of data between storage nodes without
+	  involving the compute client.  This option builds the client
+	  side, intended to be used by an upper-layer initiator such
+	  as BRMR.
+
+	  If unsure, say N.
+
+config INFINIBAND_RMR_SERVER
+	tristate "RMR server module"
+	depends on INFINIBAND_ADDR_TRANS
+	depends on INFINIBAND_RTRS_SERVER
+	select INFINIBAND_RMR
+	help
+	  RMR server module processing connection, IO and replication
+	  requests from RMR clients on top of RTRS.  It will pass IO
+	  requests to its consumer, e.g. BRMR_server.
+
+	  If unsure, say N.
diff --git a/drivers/infiniband/ulp/rmr/Makefile b/drivers/infiniband/ulp/rmr/Makefile
new file mode 100644
index 000000000000..c173092f4cf2
--- /dev/null
+++ b/drivers/infiniband/ulp/rmr/Makefile
@@ -0,0 +1,23 @@
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+ccflags-y := -I$(srctree)/drivers/infiniband/ulp/rtrs
+
+CFLAGS_rmr-clt-trace.o = -I$(src)
+
+rmr-client-y := rmr-pool.o \
+		rmr-clt.o \
+		rmr-map-mgmt.o \
+		rmr-clt-stats.o \
+		rmr-clt-sysfs.o \
+		rmr-map.o \
+		rmr-clt-trace.o
+
+rmr-server-y := rmr-pool.o \
+		rmr-srv.o \
+		rmr-srv-md.o \
+		rmr-srv-sysfs.o \
+		rmr-req.o \
+		rmr-map.o
+
+obj-$(CONFIG_INFINIBAND_RMR_CLIENT) += rmr-client.o
+obj-$(CONFIG_INFINIBAND_RMR_SERVER) += rmr-server.o
-- 
2.43.0


  parent reply	other threads:[~2026-05-05  7:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  7:46 [LSF/MM/BPF RFC PATCH 00/13] Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 01/13] RDMA/rmr: add public and private headers Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 02/13] RDMA/rmr: add shared library code (pool, map, request) Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 03/13] RDMA/rmr: client: main functionality Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 04/13] RDMA/rmr: client: sysfs interface functions Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 05/13] RDMA/rmr: server: main functionality Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 06/13] RDMA/rmr: server: sysfs interface functions Md Haris Iqbal
2026-05-05  7:46 ` Md Haris Iqbal [this message]
2026-05-05  7:46 ` [PATCH 08/13] block/brmr: add private headers with brmr protocol structs and helpers Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 09/13] block/brmr: client: main functionality Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 10/13] block/brmr: client: sysfs interface functions Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 11/13] block/brmr: server: main functionality Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 12/13] block/brmr: server: sysfs interface functions Md Haris Iqbal
2026-05-05  7:46 ` [PATCH 13/13] block/brmr: include client and server modules into kernel compilation Md Haris Iqbal

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=20260505074644.195453-8-haris.iqbal@ionos.com \
    --to=haris.iqbal@ionos.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=jgg@ziepe.ca \
    --cc=jia.li@ionos.com \
    --cc=jinpu.wang@ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.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