mm/damon/sysfs-common.c

File Facts

System

Linux kernel

Corpus path

mm/damon/sysfs-common.c

Extension

.c

Size

3262 bytes

Lines

148

Domain

Core OS

Bucket

Memory Management

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.
• 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/slab.h
• sysfs-common.h

Detected Declarations

• function min_show
• function min_store
• function max_show
• function max_store
• function damon_sysfs_ul_range_release
• function damon_sysfs_memcg_path_eq
• function damon_sysfs_memcg_path_to_id

Annotated Snippet

if (damon_sysfs_memcg_path_eq(memcg, path, memcg_path)) {
			*id = mem_cgroup_id(memcg);
			found = true;
			mem_cgroup_iter_break(NULL, memcg);
			break;
		}
	}

	kfree(path);
	return found ? 0 : -EINVAL;
}

Annotation

• Immediate include surface: `linux/slab.h`, `sysfs-common.h`.
• Detected declarations: `function min_show`, `function min_store`, `function max_show`, `function max_store`, `function damon_sysfs_ul_range_release`, `function damon_sysfs_memcg_path_eq`, `function damon_sysfs_memcg_path_to_id`.
• Atlas domain: Core OS / Memory Management.
• 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.