boot: unitload and memory-policy go, their answers stay beside the decisions - #88
Merged
Merged
Conversation
…cisions unitload compared the image against itself: the two generators it masked for the second run are masked by the image already. memory-policy's answer, min_ttl_ms, was chosen 2026-09-28 and its numbers are in lru-gen.conf and kernel/Dockerfile. The comments that named the probes name the commits that had them; ssh-load.sh's exhaust cases go with memory-policy. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
aledbf
force-pushed
the
boot/answered-unitload-memory-policy
branch
from
October 1, 2026 23:49
2a3c004 to
cbe775f
Compare
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
1 participant
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.
Two probes whose question is answered, the answer already beside the decision (the #48 precedent):
boot:unitload: it compared the image with and without two generators the image already masks (optimize-systemd.shlinks both to /dev/null), so both runs measured one configuration. The 1.0 ms result stays in optimize-systemd.sh.boot:memory-policy: min_ttl_ms was chosen 2026-09-28; the numbers are intmpfiles.d/lru-gen.confand kernel/Dockerfile. Itsgrow/exhaust*cases leave ssh-load.sh with it.The three comments that named the probes now name the commit that had them. The kernel/Dockerfile edit is a comment: the kernel lane rebuilds, and its fingerprint verdict should say vmlinux is unchanged.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.