drivers/infiniband/sw/siw/Kconfig

Source file repositories/reference/linux-study-clean/drivers/infiniband/sw/siw/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/infiniband/sw/siw/Kconfig
Extension: [no extension]
Size: 808 bytes
Lines: 21
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

config RDMA_SIW
	tristate "Software RDMA over TCP/IP (iWARP) driver"
	depends on INET && INFINIBAND
	depends on INFINIBAND_VIRT_DMA
	select CRC32
	select NET_CRC32C
	help
	This driver implements the iWARP RDMA transport over
	the Linux TCP/IP network stack. It enables a system with a
	standard Ethernet adapter to interoperate with a iWARP
	adapter or with another system running the SIW driver.
	(See also RXE which is a similar software driver for RoCE.)

	The driver interfaces with the Linux RDMA stack and
	implements both a kernel and user space RDMA verbs API.
	The user space verbs API requires a support
	library named libsiw which is loaded by the generic user
	space verbs API, libibverbs. To implement RDMA over
	TCP/IP, the driver further interfaces with the Linux
	in-kernel TCP socket layer.

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.