drivers/net/ethernet/mellanox/mlx5/core/esw/adj_vport.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/esw/adj_vport.c

Extension

.c

Size

5909 bytes

Lines

203

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

• fs_core.h
• eswitch.h

Detected Declarations

• function mlx5_esw_adj_vport_modify
• function mlx5_esw_destroy_esw_vport
• function mlx5_esw_create_esw_vport
• function mlx5_esw_adj_vport_create
• function mlx5_esw_adj_vport_destroy
• function mlx5_esw_adjacent_vhcas_cleanup
• function mlx5_esw_for_each_vf_vport
• function mlx5_esw_adjacent_vhcas_setup

Annotated Snippet

if (err) {
			esw_warn(esw->dev,
				 "Failed to init adjacent vhca 0x%x, err %d\n",
				 vhca_id, err);
			break;
		}
	}

	kvfree(out);
}

Annotation

• Immediate include surface: `fs_core.h`, `eswitch.h`.
• Detected declarations: `function mlx5_esw_adj_vport_modify`, `function mlx5_esw_destroy_esw_vport`, `function mlx5_esw_create_esw_vport`, `function mlx5_esw_adj_vport_create`, `function mlx5_esw_adj_vport_destroy`, `function mlx5_esw_adjacent_vhcas_cleanup`, `function mlx5_esw_for_each_vf_vport`, `function mlx5_esw_adjacent_vhcas_setup`.
• 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.