Repository navigation
fix!: Report from readable levels instead of None on an unreadable file - #26
Merged
Merged
Conversation
Pijukatel
reviewed
Nov 18, 2026
Pijukatel
left a comment
Contributor
There was a problem hiding this comment.
Two findings inline: on Windows a failed affinity query still drops a rate that was read fine, and ceiling shouldn't be a backend parameter.
Generated by Claude Code
Collaborator
Author
|
@Pijukatel, thanks, updated. |
Pijukatel
approved these changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
When one cgroup file could not be read, the whole reading was dropped and the answer was
None. A consumer readsNoneas "no limit" and sizes from the whole machine, which is looser than any limit that could be read.memory.max,memory.high, the CPU quota and the CPU set.cpuset.effective_cpusgives way tocpuset.cpusof the same level.usedis then a lower bound, andavailablean upper bound.*_LIMIT_UNREADABLEandMEMORY_USAGE_UNREADABLEname the file and the reason, such asmemory.max (EACCES). On Windows they name the job query and its error code.MEMORY_USAGE_UNREADABLEnow comes beside a reported budget. A level whose limit covers the machine, such as the cgroup v1 sentinel, is named only where it setsavailable.MACHINE_CPU_COUNT_UNKNOWN. The affinity is still reported.Issues
Testing
cpuset.effective_cpustocpuset.cpus;