Resource usage limits - #30
Closed
migue wants to merge 6 commits into
Closed
Conversation
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.
This patch is a working in progress where we propose the ability to spawn a new process into its own cgroup, providing the ability to limit the different set of resources it can consume (CPU, memory, ...)
The current implementation provides the ability to use the two existing implementations: cGroups V1 and the new unified hierarchy know as cGroups V2. If anyone is interested in learning more about this https://docs.kernel.org/admin-guide/cgroup-v2.html is a good resource
This is just a prototype I have put together to explore the potential benefits and drawbacks of this approach