drivers/block/rnbd/Kconfig

Source file repositories/reference/linux-study-clean/drivers/block/rnbd/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/block/rnbd/Kconfig
Extension: [no extension]
Size: 782 bytes
Lines: 30
Domain: Driver Families
Bucket: drivers/block
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 BLK_DEV_RNBD
	bool

config BLK_DEV_RNBD_CLIENT
	tristate "RDMA Network Block Device driver client"
	depends on INFINIBAND_RTRS_CLIENT
	select BLK_DEV_RNBD
	select SG_POOL
	help
	  RNBD client is a network block device driver using rdma transport.

	  RNBD client allows for mapping of a remote block devices over
	  RTRS protocol from a target system where RNBD server is running.

	  If unsure, say N.

config BLK_DEV_RNBD_SERVER
	tristate "RDMA Network Block Device driver server"
	depends on INFINIBAND_RTRS_SERVER
	select BLK_DEV_RNBD
	help
	  RNBD server is the server side of RNBD using rdma transport.

	  RNBD server allows for exporting local block devices to a remote client
	  over RTRS protocol.

	  If unsure, say N.

Annotation

Atlas domain: Driver Families / drivers/block.
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.