include/uapi/linux/rpl.h
Source file repositories/reference/linux-study-clean/include/uapi/linux/rpl.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/linux/rpl.h- Extension
.h- Size
- 864 bytes
- Lines
- 49
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/byteorder.hlinux/types.hlinux/in6.h
Detected Declarations
struct ipv6_rpl_sr_hdr
Annotated Snippet
struct ipv6_rpl_sr_hdr {
__u8 nexthdr;
__u8 hdrlen;
__u8 type;
__u8 segments_left;
#if defined(__LITTLE_ENDIAN_BITFIELD)
__u32 cmpre:4,
cmpri:4,
reserved:4,
pad:4,
reserved1:16;
#elif defined(__BIG_ENDIAN_BITFIELD)
__u32 cmpri:4,
cmpre:4,
pad:4,
reserved:20;
#else
#error "Please fix <asm/byteorder.h>"
#endif
union {
__DECLARE_FLEX_ARRAY(struct in6_addr, addr);
__DECLARE_FLEX_ARRAY(__u8, data);
} segments;
} __attribute__((packed));
#define rpl_segaddr segments.addr
#define rpl_segdata segments.data
#endif
Annotation
- Immediate include surface: `asm/byteorder.h`, `linux/types.h`, `linux/in6.h`.
- Detected declarations: `struct ipv6_rpl_sr_hdr`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source 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.