Repository navigation
The roadmap says zone weights wait on a kernel choice - #239
Merged
Merged
Conversation
….max cap a zone, and io.weight needs blk-iocost or BFQ, which the kernel does not build
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.
One line under the roadmap's "cpu and io limits": zones get caps (
cpu.max,io.max, since f085068) and no weights.io.weightneeds blk-iocost or BFQ, and the kernel builds neither (blk-throttle only), so weights wait on a kernel choice that is the owner's under the kernel-slim rule.cpu.weightalone would add little, since group scheduling already keeps a many-threaded zone from crowding zone 0.Docs only: nothing in the image changes, so no Distro run.