mm/memcontrol-v1.c

File Facts

System

Linux kernel

Corpus path

mm/memcontrol-v1.c

Extension

.c

Size

58154 bytes

Lines

2280

Domain

Core OS

Bucket

Memory Management

Inferred role

Core OS: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/memcontrol.h
• linux/swap.h
• linux/mm_inline.h
• linux/pagewalk.h
• linux/backing-dev.h
• linux/eventfd.h
• linux/poll.h
• linux/sort.h
• linux/file.h
• linux/seq_buf.h
• internal.h
• swap.h
• swap_table.h
• memcontrol-v1.h

Detected Declarations

• struct mem_cgroup_tree_per_node
• struct mem_cgroup_tree
• struct mem_cgroup_eventfd_list
• struct mem_cgroup_event
• struct memcg1_events_percpu
• struct oom_wait_info
• struct numa_stat
• enum mem_cgroup_events_target
• function __mem_cgroup_insert_exceeded
• function __mem_cgroup_remove_exceeded
• function mem_cgroup_remove_exceeded
• function soft_limit_excess
• function memcg1_update_tree
• function memcg1_remove_from_trees
• function for_each_node
• function __mem_cgroup_largest_soft_limit_node
• function mem_cgroup_largest_soft_limit_node
• function mem_cgroup_soft_reclaim
• function memcg1_soft_limit_reclaim
• function mem_cgroup_move_charge_read
• function mem_cgroup_move_charge_write
• function mem_cgroup_move_charge_write
• function mem_cgroup_usage
• function __mem_cgroup_threshold
• function mem_cgroup_threshold
• function memcg1_charge_statistics
• function memcg1_event_ratelimit
• function memcg1_check_events
• function memcg1_commit_charge
• function __memcg1_swapout
• function memcg1_swapin
• function memcg1_uncharge_batch
• function compare_thresholds
• function mem_cgroup_oom_notify_cb
• function mem_cgroup_oom_notify
• function __mem_cgroup_usage_register_event
• function mem_cgroup_usage_register_event
• function memsw_cgroup_usage_register_event
• function __mem_cgroup_usage_unregister_event
• function mem_cgroup_usage_unregister_event
• function memsw_cgroup_usage_unregister_event
• function mem_cgroup_oom_register_event
• function mem_cgroup_oom_unregister_event
• function list_for_each_entry_safe
• function memcg_event_remove
• function memcg_event_wake
• function memcg_event_ptable_queue_proc
• function memcg_write_event_control

Annotated Snippet

subsys_initcall(memcg1_init);

Annotation

• Immediate include surface: `linux/memcontrol.h`, `linux/swap.h`, `linux/mm_inline.h`, `linux/pagewalk.h`, `linux/backing-dev.h`, `linux/eventfd.h`, `linux/poll.h`, `linux/sort.h`.
• Detected declarations: `struct mem_cgroup_tree_per_node`, `struct mem_cgroup_tree`, `struct mem_cgroup_eventfd_list`, `struct mem_cgroup_event`, `struct memcg1_events_percpu`, `struct oom_wait_info`, `struct numa_stat`, `enum mem_cgroup_events_target`, `function __mem_cgroup_insert_exceeded`, `function __mem_cgroup_remove_exceeded`.
• Atlas domain: Core OS / Memory Management.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.