Documentation/ABI/removed/sysfs-kernel-uids

Source file repositories/reference/linux-study-clean/Documentation/ABI/removed/sysfs-kernel-uids

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/removed/sysfs-kernel-uids
Extension: [no extension]
Size: 698 bytes
Lines: 15
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:		/sys/kernel/uids/<uid>/cpu_shares
Date:		December 2007, finally removed in kernel v2.6.34-rc1
Contact:	Dhaval Giani <dhaval@linux.vnet.ibm.com>
		Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Description:
		The /sys/kernel/uids/<uid>/cpu_shares tunable is used
		to set the cpu bandwidth a user is allowed. This is a
		proportional value. What that means is that if there
		are two users logged in, each with an equal number of
		shares, then they will get equal CPU bandwidth. Another
		example would be, if User A has shares = 1024 and user
		B has shares = 2048, User B will get twice the CPU
		bandwidth user A will. For more details refer
		Documentation/scheduler/sched-design-CFS.rst

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

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.