drivers/net/ethernet/mellanox/mlx5/core/en/tc/int_port.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/en/tc/int_port.h

Extension

.h

Size

1958 bytes

Lines

66

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

• en.h

Detected Declarations

• struct mlx5e_tc_int_port
• struct mlx5e_tc_int_port_priv
• enum mlx5e_tc_int_port_type
• function mlx5e_tc_int_port_get_metadata_for_match
• function mlx5e_tc_int_port_get_flow_source
• function mlx5e_tc_int_port_supported
• function mlx5e_tc_int_port_init_rep_rx

Annotated Snippet

static inline void mlx5e_tc_int_port_init_rep_rx(struct mlx5e_priv *priv) {}
static inline void mlx5e_tc_int_port_cleanup_rep_rx(struct mlx5e_priv *priv) {}

#endif /* CONFIG_MLX5_CLS_ACT */
#endif /* __MLX5_EN_TC_INT_PORT_H__ */

Annotation

• Immediate include surface: `en.h`.
• Detected declarations: `struct mlx5e_tc_int_port`, `struct mlx5e_tc_int_port_priv`, `enum mlx5e_tc_int_port_type`, `function mlx5e_tc_int_port_get_metadata_for_match`, `function mlx5e_tc_int_port_get_flow_source`, `function mlx5e_tc_int_port_supported`, `function mlx5e_tc_int_port_init_rep_rx`.
• 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.