include/linux/pgalloc_tag.h

File Facts

System

Linux kernel

Corpus path

include/linux/pgalloc_tag.h

Extension

.h

Size

5319 bytes

Lines

215

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/alloc_tag.h
• linux/page_ext.h

Detected Declarations

• function module_tag_to_idx
• function module_tag_to_idx
• function idx_to_ref
• function ref_to_idx
• function get_page_tag_ref
• function put_page_tag_ref
• function update_page_tag_ref
• function clear_page_tag_ref
• function clear_page_tag_ref

Annotated Snippet

static inline void clear_page_tag_ref(struct page *page) {}
static inline void alloc_tag_sec_init(void) {}
static inline void pgalloc_tag_split(struct folio *folio, int old_order, int new_order) {}
static inline void pgalloc_tag_swap(struct folio *new, struct folio *old) {}
static inline struct alloc_tag *pgalloc_tag_get(struct page *page) { return NULL; }

#endif /* CONFIG_MEM_ALLOC_PROFILING */

#endif /* _LINUX_PGALLOC_TAG_H */

Annotation

• Immediate include surface: `linux/alloc_tag.h`, `linux/page_ext.h`.
• Detected declarations: `function module_tag_to_idx`, `function module_tag_to_idx`, `function idx_to_ref`, `function ref_to_idx`, `function get_page_tag_ref`, `function put_page_tag_ref`, `function update_page_tag_ref`, `function clear_page_tag_ref`, `function clear_page_tag_ref`.
• 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.