kernel/sched/pelt.h

File Facts

System

Linux kernel

Corpus path

kernel/sched/pelt.h

Extension

.h

Size

5611 bytes

Lines

190

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

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

• sched.h
• sched-pelt.h

Detected Declarations

• function hw_load_avg
• function update_hw_load_avg
• function hw_load_avg
• function update_irq_load_avg
• function get_pelt_divider
• function cfs_se_util_change
• function rq_clock_pelt
• function _update_idle_rq_clock_pelt
• function update_rq_clock_pelt
• function window
• function update_idle_cfs_rq_clock_pelt
• function cfs_rq_clock_pelt
• function update_idle_cfs_rq_clock_pelt

Annotated Snippet

static inline void update_idle_cfs_rq_clock_pelt(struct cfs_rq *cfs_rq) { }
static inline u64 cfs_rq_clock_pelt(struct cfs_rq *cfs_rq)
{
	return rq_clock_pelt(rq_of(cfs_rq));
}
#endif /* !CONFIG_CFS_BANDWIDTH */

#endif /* _KERNEL_SCHED_PELT_H */

Annotation

• Immediate include surface: `sched.h`, `sched-pelt.h`.
• Detected declarations: `function hw_load_avg`, `function update_hw_load_avg`, `function hw_load_avg`, `function update_irq_load_avg`, `function get_pelt_divider`, `function cfs_se_util_change`, `function rq_clock_pelt`, `function _update_idle_rq_clock_pelt`, `function update_rq_clock_pelt`, `function window`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.