drivers/net/ipvlan/ipvtap.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ipvlan/ipvtap.c

Extension

.c

Size

6065 bytes

Lines

243

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/etherdevice.h
• ipvlan.h
• linux/if_vlan.h
• linux/if_tap.h
• linux/interrupt.h
• linux/nsproxy.h
• linux/compat.h
• linux/if_tun.h
• linux/module.h
• linux/skbuff.h
• linux/cache.h
• linux/sched.h
• linux/types.h
• linux/slab.h
• linux/wait.h
• linux/cdev.h
• linux/idr.h
• linux/fs.h
• linux/uio.h
• net/net_namespace.h
• net/rtnetlink.h
• net/sock.h
• linux/virtio_net.h

Detected Declarations

• struct ipvtap_dev
• function ipvtap_count_tx_dropped
• function ipvtap_count_rx_dropped
• function ipvtap_update_features
• function ipvtap_newlink
• function ipvtap_dellink
• function ipvtap_setup
• function ipvtap_device_event
• function ipvtap_init
• function ipvtap_exit
• module init ipvtap_init

Annotated Snippet

module_init(ipvtap_init);

static void __exit ipvtap_exit(void)
{
	rtnl_link_unregister(&ipvtap_link_ops);
	unregister_netdevice_notifier(&ipvtap_notifier_block);
	class_unregister(&ipvtap_class);
	tap_destroy_cdev(ipvtap_major, &ipvtap_cdev);
}
module_exit(ipvtap_exit);
MODULE_ALIAS_RTNL_LINK("ipvtap");
MODULE_AUTHOR("Sainath Grandhi <sainath.grandhi@intel.com>");
MODULE_DESCRIPTION("IP-VLAN based tap driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/etherdevice.h`, `ipvlan.h`, `linux/if_vlan.h`, `linux/if_tap.h`, `linux/interrupt.h`, `linux/nsproxy.h`, `linux/compat.h`, `linux/if_tun.h`.
• Detected declarations: `struct ipvtap_dev`, `function ipvtap_count_tx_dropped`, `function ipvtap_count_rx_dropped`, `function ipvtap_update_features`, `function ipvtap_newlink`, `function ipvtap_dellink`, `function ipvtap_setup`, `function ipvtap_device_event`, `function ipvtap_init`, `function ipvtap_exit`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration 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.