drivers/infiniband/hw/mlx4/main.c

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/hw/mlx4/main.c

Extension

.c

Size

91169 bytes

Lines

3394

Domain

Driver Families

Bucket

drivers/infiniband

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/init.h
• linux/slab.h
• linux/errno.h
• linux/netdevice.h
• linux/inetdevice.h
• linux/rtnetlink.h
• linux/if_vlan.h
• linux/sched/mm.h
• linux/sched/task.h
• net/ipv6.h
• net/addrconf.h
• net/devlink.h
• rdma/ib_smi.h
• rdma/ib_user_verbs.h
• rdma/ib_addr.h
• rdma/ib_cache.h
• rdma/uverbs_ioctl.h
• net/bonding.h
• linux/mlx4/driver.h
• linux/mlx4/cmd.h
• linux/mlx4/qp.h
• mlx4_ib.h
• rdma/mlx4-abi.h

Detected Declarations

• struct mlx4_ib_steering
• struct default_rules
• struct diag_counter
• function check_flow_steering_support
• function num_ib_ports
• function mlx4_ib_update_gids_v1
• function mlx4_ib_update_gids_v1_v2
• function mlx4_ib_update_gids
• function free_gid_entry
• function mlx4_ib_add_gid
• function mlx4_ib_del_gid
• function mlx4_ib_gid_index_to_real_index
• function mlx4_ib_query_device
• function mlx4_ib_port_link_layer
• function ib_link_query_port
• function state_to_phys_state
• function eth_link_query_port
• function __mlx4_ib_query_port
• function mlx4_ib_query_port
• function __mlx4_ib_query_gid
• function mlx4_ib_query_gid
• function mlx4_ib_query_sl2vl
• function mlx4_init_sl2vl_tbl
• function __mlx4_ib_query_pkey
• function mlx4_ib_query_pkey
• function mlx4_ib_modify_device
• function mlx4_ib_SET_PORT
• function mlx4_ib_modify_port
• function mlx4_ib_alloc_ucontext
• function mlx4_ib_dealloc_ucontext
• function mlx4_ib_disassociate_ucontext
• function mlx4_ib_alloc_pd
• function mlx4_ib_dealloc_pd
• function mlx4_ib_alloc_xrcd
• function mlx4_ib_dealloc_xrcd
• function add_gid_entry
• function mlx4_ib_delete_counters_table
• function mlx4_ib_add_mc
• function __mlx4_ib_default_rules_match
• function __mlx4_ib_create_default_rules
• function __mlx4_ib_create_flow
• function __mlx4_ib_destroy_flow
• function mlx4_ib_tunnel_steer_add
• function mlx4_ib_add_dont_trap_rule
• function mlx4_ib_destroy_flow
• function mlx4_ib_mcg_attach
• function list_for_each_entry_safe
• function mlx4_ib_mcg_detach

Annotated Snippet

module_init(mlx4_ib_init);
module_exit(mlx4_ib_cleanup);

Annotation

• Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/slab.h`, `linux/errno.h`, `linux/netdevice.h`, `linux/inetdevice.h`, `linux/rtnetlink.h`, `linux/if_vlan.h`.
• Detected declarations: `struct mlx4_ib_steering`, `struct default_rules`, `struct diag_counter`, `function check_flow_steering_support`, `function num_ib_ports`, `function mlx4_ib_update_gids_v1`, `function mlx4_ib_update_gids_v1_v2`, `function mlx4_ib_update_gids`, `function free_gid_entry`, `function mlx4_ib_add_gid`.
• Atlas domain: Driver Families / drivers/infiniband.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.