include/linux/numa.h

File Facts

System

Linux kernel

Corpus path

include/linux/numa.h

Extension

.h

Size

1635 bytes

Lines

76

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/init.h
• linux/types.h
• linux/nodemask.h
• asm/sparsemem.h

Detected Declarations

• function numa_valid_node
• function numa_nearest_node
• function nearest_node_nodemask
• function memory_add_physaddr_to_nid
• function phys_to_target_node
• function alloc_offline_node_data

Annotated Snippet

static inline void alloc_offline_node_data(int nid) {}
#endif

#define numa_map_to_online_node(node) numa_nearest_node(node, N_ONLINE)

#ifdef CONFIG_HAVE_ARCH_NODE_DEV_GROUP
extern const struct attribute_group arch_node_dev_group;
#endif

#endif /* _LINUX_NUMA_H */

Annotation

• Immediate include surface: `linux/init.h`, `linux/types.h`, `linux/nodemask.h`, `asm/sparsemem.h`.
• Detected declarations: `function numa_valid_node`, `function numa_nearest_node`, `function nearest_node_nodemask`, `function memory_add_physaddr_to_nid`, `function phys_to_target_node`, `function alloc_offline_node_data`.
• 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.