drivers/net/ethernet/cavium/liquidio/lio_vf_rep.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/cavium/liquidio/lio_vf_rep.h

Extension

.h

Size

1573 bytes

Lines

50

Domain

Driver Families

Bucket

drivers/net

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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 lio_vf_rep_desc
• struct lio_vf_rep_sc_ctx

Annotated Snippet

struct lio_vf_rep_desc {
	struct net_device *parent_ndev;
	struct net_device *ndev;
	struct octeon_device *oct;
	struct lio_vf_rep_stats stats;
	struct cavium_wk stats_wk;
	atomic_t ifstate;
	int ifidx;
};

struct lio_vf_rep_sc_ctx {
	struct completion complete;
};

int lio_vf_rep_create(struct octeon_device *oct);
void lio_vf_rep_destroy(struct octeon_device *oct);
int lio_vf_rep_modinit(void);
void lio_vf_rep_modexit(void);
#endif

Annotation

• Detected declarations: `struct lio_vf_rep_desc`, `struct lio_vf_rep_sc_ctx`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.