drivers/net/ethernet/alibaba/eea/eea_ethtool.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/alibaba/eea/eea_ethtool.h

Extension

.h

Size

910 bytes

Lines

49

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.
• 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 eea_tx_stats
• struct eea_rx_ctx_stats
• struct eea_rx_stats

Annotated Snippet

struct eea_tx_stats {
	struct u64_stats_sync syncp;
	u64_stats_t descs;
	u64_stats_t packets;
	u64_stats_t bytes;
	u64_stats_t drops;
	u64_stats_t kicks;
};

struct eea_rx_ctx_stats {
	u64 descs;
	u64 packets;
	u64 bytes;
	u64 drops;
	u64 split_hdr_bytes;
	u64 split_hdr_packets;
	u64 kicks;
	u64 length_errors;
};

struct eea_rx_stats {
	struct u64_stats_sync syncp;
	u64_stats_t descs;
	u64_stats_t packets;
	u64_stats_t bytes;
	u64_stats_t drops;
	u64_stats_t kicks;
	u64_stats_t split_hdr_bytes;
	u64_stats_t split_hdr_packets;

	u64_stats_t length_errors;
};

void eea_update_rx_stats(struct eea_rx_stats *rx_stats,
			 struct eea_rx_ctx_stats *stats);

extern const struct ethtool_ops eea_ethtool_ops;
#endif

Annotation

• Detected declarations: `struct eea_tx_stats`, `struct eea_rx_ctx_stats`, `struct eea_rx_stats`.
• Atlas domain: Driver Families / drivers/net.
• 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.