drivers/infiniband/ulp/rtrs/Kconfig

Source file repositories/reference/linux-study-clean/drivers/infiniband/ulp/rtrs/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/infiniband/ulp/rtrs/Kconfig
Extension: [no extension]
Size: 809 bytes
Lines: 28
Domain: Driver Families
Bucket: drivers/infiniband
Inferred role: Driver Families: build/configuration rule
Status: atlas-only

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-or-later

config INFINIBAND_RTRS
	tristate
	depends on INFINIBAND_ADDR_TRANS

config INFINIBAND_RTRS_CLIENT
	tristate "RTRS client module"
	depends on INFINIBAND_ADDR_TRANS
	select INFINIBAND_RTRS
	help
	  RDMA transport client module.

	  RDMA Transport (RTRS) client implements a reliable transport layer
	  and also multipathing functionality and that it is intended to be
	  the base layer for a block storage initiator over RDMA.

config INFINIBAND_RTRS_SERVER
	tristate "RTRS server module"
	depends on INFINIBAND_ADDR_TRANS
	select INFINIBAND_RTRS
	help
	  RDMA transport server module.

	  RDMA Transport (RTRS) server module processing connection and IO
	  requests received from the RTRS client module, it will pass the
	  IO requests to its user eg. RNBD_server.

Annotation

Atlas domain: Driver Families / drivers/infiniband.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.