net/rds/Kconfig

Source file repositories/reference/linux-study-clean/net/rds/Kconfig

File Facts

System: Linux kernel
Corpus path: net/rds/Kconfig
Extension: [no extension]
Size: 908 bytes
Lines: 38
Domain: Networking Core
Bucket: Sockets, Protocols, Packet Path, And Network Policy
Inferred role: Networking Core: build/configuration rule
Status: atlas-only

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

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-only

config RDS
	tristate "The Reliable Datagram Sockets Protocol"
	depends on INET
	help
	  The RDS (Reliable Datagram Sockets) protocol provides reliable,
	  sequenced delivery of datagrams over Infiniband or TCP.

config RDS_RDMA
	tristate "RDS over Infiniband"
	depends on RDS && INFINIBAND && INFINIBAND_ADDR_TRANS
	help
	  Allow RDS to use Infiniband as a transport.
	  This transport supports RDMA operations.

config RDS_TCP
	tristate "RDS over TCP"
	depends on RDS
	depends on IPV6 || !IPV6
	help
	  Allow RDS to use TCP as a transport.
	  This transport does not support RDMA operations.

config RDS_DEBUG
	bool "RDS debugging messages"
	depends on RDS
	default n

config GCOV_PROFILE_RDS
	bool "Enable GCOV profiling on RDS"
	depends on GCOV_KERNEL
	help
	  Enable GCOV profiling on RDS for checking which functions/lines
	  are executed.

	  If unsure, say N.

Annotation

Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
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.