net/openvswitch/vport-gre.c
Source file repositories/reference/linux-study-clean/net/openvswitch/vport-gre.c
File Facts
- System
- Linux kernel
- Corpus path
net/openvswitch/vport-gre.c- Extension
.c- Size
- 2282 bytes
- Lines
- 107
- 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/if.hlinux/skbuff.hlinux/ip.hlinux/if_tunnel.hlinux/if_vlan.hlinux/in.hlinux/in_route.hlinux/inetdevice.hlinux/jhash.hlinux/list.hlinux/kernel.hlinux/module.hlinux/workqueue.hlinux/rculist.hnet/route.hnet/xfrm.hnet/icmp.hnet/ip.hnet/ip_tunnels.hnet/gre.hnet/net_namespace.hnet/netns/generic.hnet/protocol.hdatapath.hvport.hvport-netdev.h
Detected Declarations
function ovs_gre_tnl_initfunction ovs_gre_tnl_exitmodule init ovs_gre_tnl_init
Annotated Snippet
module_init(ovs_gre_tnl_init);
module_exit(ovs_gre_tnl_exit);
MODULE_DESCRIPTION("OVS: GRE switching port");
MODULE_LICENSE("GPL");
MODULE_ALIAS("vport-type-3");
Annotation
- Immediate include surface: `linux/if.h`, `linux/skbuff.h`, `linux/ip.h`, `linux/if_tunnel.h`, `linux/if_vlan.h`, `linux/in.h`, `linux/in_route.h`, `linux/inetdevice.h`.
- Detected declarations: `function ovs_gre_tnl_init`, `function ovs_gre_tnl_exit`, `module init ovs_gre_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.