include/net/eee.h

File Facts

System

Linux kernel

Corpus path

include/net/eee.h

Extension

.h

Size

832 bytes

Lines

36

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: implementation source

Status

source implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h

Detected Declarations

• struct eee_config
• function eeecfg_mac_can_tx_lpi
• function eeecfg_to_eee
• function eee_to_eeecfg

Annotated Snippet

struct eee_config {
	u32 tx_lpi_timer;
	bool tx_lpi_enabled;
	bool eee_enabled;
};

static inline bool eeecfg_mac_can_tx_lpi(const struct eee_config *eeecfg)
{
	/* eee_enabled is the master on/off */
	return eeecfg->eee_enabled && eeecfg->tx_lpi_enabled;
}

static inline void eeecfg_to_eee(struct ethtool_keee *eee,
				 const struct eee_config *eeecfg)
{
	eee->tx_lpi_timer = eeecfg->tx_lpi_timer;
	eee->tx_lpi_enabled = eeecfg->tx_lpi_enabled;
	eee->eee_enabled = eeecfg->eee_enabled;
}

static inline void eee_to_eeecfg(struct eee_config *eeecfg,
				 const struct ethtool_keee *eee)
{
	eeecfg->tx_lpi_timer = eee->tx_lpi_timer;
	eeecfg->tx_lpi_enabled = eee->tx_lpi_enabled;
	eeecfg->eee_enabled = eee->eee_enabled;
}

#endif

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct eee_config`, `function eeecfg_mac_can_tx_lpi`, `function eeecfg_to_eee`, `function eee_to_eeecfg`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• 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.