include/net/net_failover.h

File Facts

System

Linux kernel

Corpus path

include/net/net_failover.h

Extension

.h

Size

1023 bytes

Lines

41

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

• net/failover.h

Detected Declarations

• struct net_failover_info

Annotated Snippet

struct net_failover_info {
	/* primary netdev with same MAC */
	struct net_device __rcu *primary_dev;

	/* standby netdev */
	struct net_device __rcu *standby_dev;

	/* primary netdev stats */
	struct rtnl_link_stats64 primary_stats;

	/* standby netdev stats */
	struct rtnl_link_stats64 standby_stats;

	/* aggregated stats */
	struct rtnl_link_stats64 failover_stats;

	/* spinlock while updating stats */
	spinlock_t stats_lock;
};

struct failover *net_failover_create(struct net_device *standby_dev);
void net_failover_destroy(struct failover *failover);

#define FAILOVER_VLAN_FEATURES	(NETIF_F_HW_CSUM | NETIF_F_SG | \
				 NETIF_F_FRAGLIST | NETIF_F_ALL_TSO | \
				 NETIF_F_HIGHDMA | NETIF_F_LRO)

#define FAILOVER_ENC_FEATURES	(NETIF_F_HW_CSUM | NETIF_F_SG | \
				 NETIF_F_RXCSUM | NETIF_F_ALL_TSO)

#endif /* _NET_FAILOVER_H */

Annotation

• Immediate include surface: `net/failover.h`.
• Detected declarations: `struct net_failover_info`.
• 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.