net/openvswitch/vport-vxlan.c

File Facts

System

Linux kernel

Corpus path

net/openvswitch/vport-vxlan.c

Extension

.c

Size

3857 bytes

Lines

173

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/skbuff.h
• linux/openvswitch.h
• linux/module.h
• net/udp.h
• net/ip_tunnels.h
• net/rtnetlink.h
• net/vxlan.h
• datapath.h
• vport.h
• vport-netdev.h

Detected Declarations

• function vxlan_get_options
• function vxlan_configure_exts
• function ovs_vxlan_tnl_init
• function ovs_vxlan_tnl_exit
• module init ovs_vxlan_tnl_init

Annotated Snippet

module_init(ovs_vxlan_tnl_init);
module_exit(ovs_vxlan_tnl_exit);

MODULE_DESCRIPTION("OVS: VXLAN switching port");
MODULE_LICENSE("GPL");
MODULE_ALIAS("vport-type-4");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/skbuff.h`, `linux/openvswitch.h`, `linux/module.h`, `net/udp.h`, `net/ip_tunnels.h`, `net/rtnetlink.h`, `net/vxlan.h`.
• Detected declarations: `function vxlan_get_options`, `function vxlan_configure_exts`, `function ovs_vxlan_tnl_init`, `function ovs_vxlan_tnl_exit`, `module init ovs_vxlan_tnl_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.