drivers/nvme/target/fc.c

File Facts

System

Linux kernel

Corpus path

drivers/nvme/target/fc.c

Extension

.c

Size

82010 bytes

Lines

3027

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/module.h
• linux/slab.h
• linux/blk-mq.h
• linux/parser.h
• linux/random.h
• uapi/scsi/fc/fc_fs.h
• uapi/scsi/fc/fc_els.h
• nvmet.h
• linux/nvme-fc-driver.h
• linux/nvme-fc.h
• ../host/fc.h

Detected Declarations

• struct nvmet_fc_tgtport
• struct nvmet_fc_tgt_assoc
• struct nvmet_fc_ls_iod
• struct nvmet_fc_ls_req_op
• struct nvmet_fc_fcp_iod
• struct nvmet_fc_tgtport
• struct nvmet_fc_port_entry
• struct nvmet_fc_defer_fcp_req
• struct nvmet_fc_tgt_queue
• struct nvmet_fc_hostport
• struct nvmet_fc_tgt_assoc
• struct nvmet_fc_traddr
• enum nvmet_fcp_datadir
• function nvmet_fc_makeconnid
• function nvmet_fc_getassociationid
• function nvmet_fc_getqueueid
• function targetport_to_tgtport
• function nvmet_req_to_fod
• function nvmet_fc_put_lsop_work
• function mappings
• function fc_dma_mapping_error
• function fc_dma_unmap_single
• function fc_dma_sync_single_for_cpu
• function fc_dma_sync_single_for_device
• function fc_map_sg
• function for_each_sg
• function fc_dma_map_sg
• function fc_dma_unmap_sg
• function __nvmet_fc_finish_ls_req
• function __nvmet_fc_send_ls_req
• function nvmet_fc_send_ls_req_async
• function nvmet_fc_disconnect_assoc_done
• function nvmet_fc_xmt_disconnect_assoc
• function nvmet_fc_alloc_ls_iodlist
• function nvmet_fc_free_ls_iodlist
• function nvmet_fc_alloc_ls_iod
• function nvmet_fc_free_ls_iod
• function nvmet_fc_prep_fcp_iodlist
• function nvmet_fc_destroy_fcp_iodlist
• function nvmet_fc_alloc_fcp_iod
• function nvmet_fc_queue_fcp_req
• function nvmet_fc_fcp_rqst_op_defer_work
• function nvmet_fc_free_fcp_iod
• function nvmet_fc_alloc_target_queue
• function nvmet_fc_tgt_queue_free
• function nvmet_fc_tgt_q_put
• function nvmet_fc_tgt_q_get
• function nvmet_fc_delete_target_queue

Annotated Snippet

module_init(nvmet_fc_init_module);
module_exit(nvmet_fc_exit_module);

MODULE_DESCRIPTION("NVMe target FC transport driver");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/module.h`, `linux/slab.h`, `linux/blk-mq.h`, `linux/parser.h`, `linux/random.h`, `uapi/scsi/fc/fc_fs.h`, `uapi/scsi/fc/fc_els.h`, `nvmet.h`.
• Detected declarations: `struct nvmet_fc_tgtport`, `struct nvmet_fc_tgt_assoc`, `struct nvmet_fc_ls_iod`, `struct nvmet_fc_ls_req_op`, `struct nvmet_fc_fcp_iod`, `struct nvmet_fc_tgtport`, `struct nvmet_fc_port_entry`, `struct nvmet_fc_defer_fcp_req`, `struct nvmet_fc_tgt_queue`, `struct nvmet_fc_hostport`.
• 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.