drivers/infiniband/ulp/srpt/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/infiniband/ulp/srpt/Kconfig
Extension: [no extension]
Size: 644 bytes
Lines: 14
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-only
config INFINIBAND_SRPT
	tristate "InfiniBand SCSI RDMA Protocol target support"
	depends on INFINIBAND && INFINIBAND_ADDR_TRANS && TARGET_CORE
	help

	  Support for the SCSI RDMA Protocol (SRP) Target driver. The
	  SRP protocol is a protocol that allows an initiator to access
	  a block storage device on another host (target) over a network
	  that supports the RDMA protocol. Currently the RDMA protocol is
	  supported by InfiniBand and by iWarp network hardware. More
	  information about the SRP protocol can be found on the website
	  of the INCITS T10 technical committee (http://www.t10.org/).

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.