libct/cg/fs: don't write cpu_burst twice on ENOENT #4259
Merged
Conversation
This file contains 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
If CPU burst knob is non-existent, the current implementation (added in commit e158483) still tries to set it again after setting the new CPU quota, which is useless (and we have to ignore ENOENT again). Fix this. Signed-off-by: Kir Kolyshkin <[email protected]>
kolyshkin
force-pushed
the
fix-cpu-burst
branch
from
7a2e2b8
to
b032fea
Compare
lifubang
approved these changes
Apr 27, 2024
AkihiroSuda
approved these changes
Apr 27, 2024
Merged
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.
If CPU burst knob is non-existent, the current implementation (added in commit e158483, PR #3749) still tries to set it again after setting the new CPU quota, which is useless (and we have to ignore ENOENT again).
Fix this.