drivers/nvme/target/rdma.c

File Facts

System

Linux kernel

Corpus path

drivers/nvme/target/rdma.c

Extension

.c

Size

53966 bytes

Lines

2133

Domain

Representative Device Path

Bucket

PCIe NVMe Storage Path

Inferred role

Representative Device Path: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• linux/blk-integrity.h
• linux/ctype.h
• linux/delay.h
• linux/err.h
• linux/init.h
• linux/module.h
• linux/nvme.h
• linux/slab.h
• linux/string.h
• linux/wait.h
• linux/inet.h
• linux/unaligned.h
• rdma/ib_verbs.h
• rdma/rdma_cm.h
• rdma/rw.h
• rdma/ib_cm.h
• linux/nvme-rdma.h
• nvmet.h

Detected Declarations

• struct nvmet_rdma_srq
• struct nvmet_rdma_cmd
• struct nvmet_rdma_rsp
• struct nvmet_rdma_queue
• struct nvmet_rdma_port
• struct nvmet_rdma_srq
• struct nvmet_rdma_device
• enum nvmet_rdma_queue_state
• function srq_size_set
• function num_pages
• function nvmet_rdma_need_data_in
• function nvmet_rdma_need_data_out
• function nvmet_rdma_get_rsp
• function nvmet_rdma_put_rsp
• function nvmet_rdma_free_inline_pages
• function nvmet_rdma_alloc_inline_pages
• function nvmet_rdma_alloc_cmd
• function nvmet_rdma_free_cmd
• function nvmet_rdma_alloc_cmds
• function nvmet_rdma_free_cmds
• function nvmet_rdma_alloc_rsp
• function nvmet_rdma_free_rsp
• function nvmet_rdma_alloc_rsps
• function nvmet_rdma_free_rsps
• function nvmet_rdma_post_recv
• function nvmet_rdma_process_wr_wait_list
• function nvmet_rdma_check_pi_status
• function nvmet_rdma_set_sig_domain
• function nvmet_rdma_set_sig_attrs
• function nvmet_rdma_rw_ctx_init
• function nvmet_rdma_rw_ctx_destroy
• function nvmet_rdma_release_rsp
• function nvmet_rdma_error_comp
• function nvmet_rdma_send_done
• function nvmet_rdma_queue_response
• function nvmet_rdma_read_data_done
• function nvmet_rdma_write_data_done
• function nvmet_rdma_use_inline_sg
• function nvmet_rdma_map_sgl_inline
• function nvmet_rdma_map_sgl_keyed
• function nvmet_rdma_map_sgl
• function nvmet_rdma_execute_command
• function nvmet_rdma_handle_command
• function nvmet_rdma_recv_not_live
• function nvmet_rdma_recv_done
• function nvmet_rdma_destroy_srq
• function nvmet_rdma_destroy_srqs
• function nvmet_rdma_init_srq

Annotated Snippet

module_init(nvmet_rdma_init);
module_exit(nvmet_rdma_exit);

MODULE_DESCRIPTION("NVMe target RDMA transport driver");
MODULE_LICENSE("GPL v2");
MODULE_ALIAS("nvmet-transport-1"); /* 1 == NVMF_TRTYPE_RDMA */

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/blk-integrity.h`, `linux/ctype.h`, `linux/delay.h`, `linux/err.h`, `linux/init.h`, `linux/module.h`, `linux/nvme.h`.
• Detected declarations: `struct nvmet_rdma_srq`, `struct nvmet_rdma_cmd`, `struct nvmet_rdma_rsp`, `struct nvmet_rdma_queue`, `struct nvmet_rdma_port`, `struct nvmet_rdma_srq`, `struct nvmet_rdma_device`, `enum nvmet_rdma_queue_state`, `function srq_size_set`, `function num_pages`.
• Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.