include/linux/nvme-rdma.h

File Facts

System

Linux kernel

Corpus path

include/linux/nvme-rdma.h

Extension

.h

Size

2366 bytes

Lines

98

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: implementation source

Status

source implementation candidate

Why This File Exists

Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.

• Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct nvme_rdma_cm_req
• struct nvme_rdma_cm_rep
• struct nvme_rdma_cm_rej
• enum nvme_rdma_cm_fmt
• enum nvme_rdma_cm_status

Annotated Snippet

struct nvme_rdma_cm_req {
	__le16		recfmt;
	__le16		qid;
	__le16		hrqsize;
	__le16		hsqsize;
	__le16		cntlid;
	u8		rsvd[22];
};

/**
 * struct nvme_rdma_cm_rep - rdma connect reply
 *
 * @recfmt:        format of the RDMA Private Data
 * @crqsize:       controller receive queue size
 */
struct nvme_rdma_cm_rep {
	__le16		recfmt;
	__le16		crqsize;
	u8		rsvd[28];
};

/**
 * struct nvme_rdma_cm_rej - rdma connect reject
 *
 * @recfmt:        format of the RDMA Private Data
 * @sts:           error status for the associated connect request
 */
struct nvme_rdma_cm_rej {
	__le16		recfmt;
	__le16		sts;
};

#endif /* _LINUX_NVME_RDMA_H */

Annotation

• Detected declarations: `struct nvme_rdma_cm_req`, `struct nvme_rdma_cm_rep`, `struct nvme_rdma_cm_rej`, `enum nvme_rdma_cm_fmt`, `enum nvme_rdma_cm_status`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• Implementation status: source implementation candidate.

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.