drivers/infiniband/hw/irdma/main.c

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/hw/irdma/main.c

Extension

.c

Size

6390 bytes

Lines

212

Domain

Driver Families

Bucket

drivers/infiniband

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• main.h
• linux/net/intel/iidc_rdma_idpf.h

Detected Declarations

• function irdma_register_notifiers
• function irdma_unregister_notifiers
• function irdma_log_invalid_mtu
• function ig3rdma_idc_vport_event_handler
• function ig3rdma_vport_probe
• function ig3rdma_vport_remove
• function irdma_init_module
• function irdma_exit_module
• module init irdma_init_module

Annotated Snippet

module_init(irdma_init_module);
module_exit(irdma_exit_module);

Annotation

• Immediate include surface: `main.h`, `linux/net/intel/iidc_rdma_idpf.h`.
• Detected declarations: `function irdma_register_notifiers`, `function irdma_unregister_notifiers`, `function irdma_log_invalid_mtu`, `function ig3rdma_idc_vport_event_handler`, `function ig3rdma_vport_probe`, `function ig3rdma_vport_remove`, `function irdma_init_module`, `function irdma_exit_module`, `module init irdma_init_module`.
• Atlas domain: Driver Families / drivers/infiniband.
• Implementation status: integration 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.