include/linux/psi.h

File Facts

System

Linux kernel

Corpus path

include/linux/psi.h

Extension

.h

Size

1824 bytes

Lines

71

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

• linux/jump_label.h
• linux/psi_types.h
• linux/sched.h
• linux/poll.h
• linux/cgroup-defs.h
• linux/cgroup.h

Detected Declarations

• struct seq_file
• struct css_set
• function psi_init
• function psi_cgroup_free
• function psi_cgroup_restart

Annotated Snippet

static inline void psi_init(void) {}

static inline void psi_memstall_enter(unsigned long *flags) {}
static inline void psi_memstall_leave(unsigned long *flags) {}

#ifdef CONFIG_CGROUPS
static inline int psi_cgroup_alloc(struct cgroup *cgrp)
{
	return 0;
}
static inline void psi_cgroup_free(struct cgroup *cgrp)
{
}
static inline void cgroup_move_task(struct task_struct *p, struct css_set *to)
{
	rcu_assign_pointer(p->cgroups, to);
}
static inline void psi_cgroup_restart(struct psi_group *group) {}
#endif

#endif /* CONFIG_PSI */

#endif /* _LINUX_PSI_H */

Annotation

• Immediate include surface: `linux/jump_label.h`, `linux/psi_types.h`, `linux/sched.h`, `linux/poll.h`, `linux/cgroup-defs.h`, `linux/cgroup.h`.
• Detected declarations: `struct seq_file`, `struct css_set`, `function psi_init`, `function psi_cgroup_free`, `function psi_cgroup_restart`.
• 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.