drivers/net/team/team_mode_roundrobin.c

File Facts

System

Linux kernel

Corpus path

drivers/net/team/team_mode_roundrobin.c

Extension

.c

Size

1748 bytes

Lines

76

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/types.h
• linux/module.h
• linux/init.h
• linux/netdevice.h
• linux/if_team.h

Detected Declarations

• struct rr_priv
• function rr_transmit
• function rr_init_module
• function rr_cleanup_module
• module init rr_init_module

Annotated Snippet

module_init(rr_init_module);
module_exit(rr_cleanup_module);

MODULE_LICENSE("GPL v2");
MODULE_AUTHOR("Jiri Pirko <jpirko@redhat.com>");
MODULE_DESCRIPTION("Round-robin mode for team");
MODULE_ALIAS_TEAM_MODE("roundrobin");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/types.h`, `linux/module.h`, `linux/init.h`, `linux/netdevice.h`, `linux/if_team.h`.
• Detected declarations: `struct rr_priv`, `function rr_transmit`, `function rr_init_module`, `function rr_cleanup_module`, `module init rr_init_module`.
• Atlas domain: Driver Families / drivers/net.
• 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.