include/net/netfilter/xt_rateest.h

File Facts

System

Linux kernel

Corpus path

include/net/netfilter/xt_rateest.h

Extension

.h

Size

717 bytes

Lines

28

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• net/gen_stats.h

Detected Declarations

• struct xt_rateest

Annotated Snippet

struct xt_rateest {
	/* keep lock and bstats on same cache line to speedup xt_rateest_tg() */
	struct gnet_stats_basic_sync	bstats;
	spinlock_t			lock;


	/* following fields not accessed in hot path */
	unsigned int			refcnt;
	struct hlist_node		list;
	char				name[IFNAMSIZ];
	struct gnet_estimator		params;
	struct rcu_head			rcu;

	/* keep this field far away to speedup xt_rateest_mt() */
	struct net_rate_estimator __rcu *rate_est;
};

struct xt_rateest *xt_rateest_lookup(struct net *net, const char *name);
void xt_rateest_put(struct net *net, struct xt_rateest *est);

#endif /* _XT_RATEEST_H */

Annotation

• Immediate include surface: `net/gen_stats.h`.
• Detected declarations: `struct xt_rateest`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: source implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.