Documentation/netlink/specs/rt-link.yaml
Source file repositories/reference/linux-study-clean/Documentation/netlink/specs/rt-link.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/netlink/specs/rt-link.yaml- Extension
.yaml- Size
- 48133 bytes
- Lines
- 2602
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
---
name: rt-link
protocol: netlink-raw
uapi-header: linux/rtnetlink.h
protonum: 0
doc: >-
Link configuration over rtnetlink.
definitions:
-
name: ifinfo-flags
type: flags
header: linux/if.h
enum-name: net-device-flags
name-prefix: iff-
entries:
-
name: up
-
name: broadcast
-
name: debug
-
name: loopback
-
name: point-to-point
-
name: no-trailers
-
name: running
-
name: no-arp
-
name: promisc
-
name: all-multi
-
name: master
-
name: slave
-
name: multicast
-
name: portsel
-
name: auto-media
-
name: dynamic
-
name: lower-up
-
name: dormant
-
name: echo
-
name: vlan-protocols
type: enum
enum-name:
entries:
-
name: 8021q
value: 33024
-
name: 8021ad
value: 34984
-
name: rtgenmsg
type: struct
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
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.