drivers/net/ethernet/mellanox/mlx5/core/lib/port_tun.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/lib/port_tun.h

Extension

.h

Size

706 bytes

Lines

25

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

• linux/mlx5/driver.h

Detected Declarations

• struct mlx5_tun_entropy

Annotated Snippet

struct mlx5_tun_entropy {
	struct mlx5_core_dev *mdev;
	u32 num_enabling_entries;
	u32 num_disabling_entries;
	u8  enabled;
	struct mutex lock;	/* lock the entropy fields */
};

void mlx5_init_port_tun_entropy(struct mlx5_tun_entropy *tun_entropy,
				struct mlx5_core_dev *mdev);
int mlx5_tun_entropy_refcount_inc(struct mlx5_tun_entropy *tun_entropy,
				  int reformat_type);
void mlx5_tun_entropy_refcount_dec(struct mlx5_tun_entropy *tun_entropy,
				   int reformat_type);

#endif /* __MLX5_PORT_TUN_H__ */

Annotation

• Immediate include surface: `linux/mlx5/driver.h`.
• Detected declarations: `struct mlx5_tun_entropy`.
• 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.