drivers/target/tcm_remote/tcm_remote.h

File Facts

System

Linux kernel

Corpus path

drivers/target/tcm_remote/tcm_remote.h

Extension

.h

Size

506 bytes

Lines

21

Domain

Driver Families

Bucket

drivers/target

Inferred role

Driver Families: implementation source

Status

source implementation candidate

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• linux/device.h

Detected Declarations

• struct tcm_remote_tpg
• struct tcm_remote_hba

Annotated Snippet

struct tcm_remote_tpg {
	unsigned short remote_tpgt;
	struct se_portal_group remote_se_tpg;
	struct tcm_remote_hba *remote_hba;
};

struct tcm_remote_hba {
	u8 remote_proto_id;
	unsigned char remote_wwn_address[TL_WWN_ADDR_LEN];
	struct tcm_remote_tpg remote_hba_tpgs[TL_TPGS_PER_HBA];
	struct se_wwn remote_hba_wwn;
};

Annotation

• Immediate include surface: `linux/types.h`, `linux/device.h`.
• Detected declarations: `struct tcm_remote_tpg`, `struct tcm_remote_hba`.
• Atlas domain: Driver Families / drivers/target.
• 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.