net/openvswitch/vport-geneve.c

Source file repositories/reference/linux-study-clean/net/openvswitch/vport-geneve.c

File Facts

System: Linux kernel
Corpus path: net/openvswitch/vport-geneve.c
Extension: .c
Size: 3080 bytes
Lines: 144
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/in.h
linux/ip.h
linux/net.h
linux/rculist.h
linux/udp.h
linux/if_vlan.h
linux/module.h
net/geneve.h
net/icmp.h
net/ip.h
net/route.h
net/udp.h
net/xfrm.h
datapath.h
vport.h
vport-netdev.h

Detected Declarations

struct geneve_port
function geneve_get_options
function ovs_geneve_tnl_init
function ovs_geneve_tnl_exit
module init ovs_geneve_tnl_init

Annotated Snippet

module_init(ovs_geneve_tnl_init);
module_exit(ovs_geneve_tnl_exit);

MODULE_DESCRIPTION("OVS: Geneve switching port");
MODULE_LICENSE("GPL");
MODULE_ALIAS("vport-type-5");

Annotation

Immediate include surface: `linux/in.h`, `linux/ip.h`, `linux/net.h`, `linux/rculist.h`, `linux/udp.h`, `linux/if_vlan.h`, `linux/module.h`, `net/geneve.h`.
Detected declarations: `struct geneve_port`, `function geneve_get_options`, `function ovs_geneve_tnl_init`, `function ovs_geneve_tnl_exit`, `module init ovs_geneve_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.