drivers/infiniband/hw/mlx5/macsec.h

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/hw/mlx5/macsec.h

Extension

.h

Size

1245 bytes

Lines

30

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

• net/macsec.h
• rdma/ib_cache.h
• rdma/ib_addr.h
• mlx5_ib.h

Detected Declarations

• struct mlx5_reserved_gids
• function mlx5r_add_gid_macsec_operations
• function mlx5r_del_gid_macsec_operations
• function mlx5r_macsec_dealloc_gids

Annotated Snippet

static inline int mlx5r_add_gid_macsec_operations(const struct ib_gid_attr *attr) { return 0; }
static inline void mlx5r_del_gid_macsec_operations(const struct ib_gid_attr *attr) {}
static inline int mlx5r_macsec_init_gids_and_devlist(struct mlx5_ib_dev *dev) { return 0; }
static inline void mlx5r_macsec_dealloc_gids(struct mlx5_ib_dev *dev) {}
static inline void mlx5r_macsec_event_register(struct mlx5_ib_dev *dev) {}
static inline void mlx5r_macsec_event_unregister(struct mlx5_ib_dev *dev) {}
#endif
#endif /* __MLX5_MACSEC_H__ */

Annotation

• Immediate include surface: `net/macsec.h`, `rdma/ib_cache.h`, `rdma/ib_addr.h`, `mlx5_ib.h`.
• Detected declarations: `struct mlx5_reserved_gids`, `function mlx5r_add_gid_macsec_operations`, `function mlx5r_del_gid_macsec_operations`, `function mlx5r_macsec_dealloc_gids`.
• 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.