drivers/infiniband/hw/mlx5/ib_rep.h
Source file repositories/reference/linux-study-clean/drivers/infiniband/hw/mlx5/ib_rep.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/infiniband/hw/mlx5/ib_rep.h- Extension
.h- Size
- 1043 bytes
- Lines
- 41
- Domain
- Driver Families
- Bucket
- drivers/infiniband
- 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/eswitch.hmlx5_ib.h
Detected Declarations
function mlx5r_rep_initfunction mlx5r_rep_cleanup
Annotated Snippet
static inline int mlx5r_rep_init(void) { return 0; }
static inline void mlx5r_rep_cleanup(void) {}
static inline
struct mlx5_flow_handle *create_flow_rule_vport_sq(struct mlx5_ib_dev *dev,
struct mlx5_ib_sq *sq,
u32 port)
{
return NULL;
}
static inline
struct net_device *mlx5_ib_get_rep_netdev(struct mlx5_eswitch *esw,
u16 vport_num)
{
return NULL;
}
#endif
#endif /* __MLX5_IB_REP_H__ */
Annotation
- Immediate include surface: `linux/mlx5/eswitch.h`, `mlx5_ib.h`.
- Detected declarations: `function mlx5r_rep_init`, `function mlx5r_rep_cleanup`.
- Atlas domain: Driver Families / drivers/infiniband.
- 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.