drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/netronome/nfp/nfp_netvf_main.c

Extension

.c

Size

8819 bytes

Lines

345

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/kernel.h
• linux/init.h
• linux/etherdevice.h
• nfpcore/nfp_dev.h
• nfp_net_ctrl.h
• nfp_net.h
• nfp_main.h

Detected Declarations

• struct nfp_net_vf
• function nfp_netvf_get_mac_addr
• function nfp_netvf_pci_probe
• function nfp_netvf_pci_remove

Annotated Snippet

struct pci_driver nfp_netvf_pci_driver = {
	.name        = nfp_net_driver_name,
	.id_table    = nfp_netvf_pci_device_ids,
	.probe       = nfp_netvf_pci_probe,
	.remove      = nfp_netvf_pci_remove,
	.shutdown    = nfp_netvf_pci_remove,
};

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/etherdevice.h`, `nfpcore/nfp_dev.h`, `nfp_net_ctrl.h`, `nfp_net.h`, `nfp_main.h`.
• Detected declarations: `struct nfp_net_vf`, `function nfp_netvf_get_mac_addr`, `function nfp_netvf_pci_probe`, `function nfp_netvf_pci_remove`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: pattern implementation candidate.
• 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.