-
Notifications
You must be signed in to change notification settings - Fork 554
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config-linux: Drop redundant 'blkio' prefix from blockIO properties #860
config-linux: Drop redundant 'blkio' prefix from blockIO properties #860
Conversation
f156aca
to
a70bd8f
Compare
I tend to keep them close to cgroup APIs, so +1 for closing this PR. |
If we want this before 2.0, it needs to go in the 1.0.0 milestone. If we don't want this before 2.0, and are ok with the currently-inconsistent controller-prefixing, then maintainers should close this issue with a note to that effect. The current maintainer comment seems to be in favor of controller-prefixing, and if we want to do that consistently (we don't at the moment, currently only for the |
These are long enough without the prefix, and linux.resources.blockIO.blkioWeight, etc. are just as specific as linux.resources.blockIO.weight. Generated with: $ sed -i s/blkioWeight/weight/g $(git grep -l blkioWeight) $ sed -i s/blkioLeaf/leaf/g $(git grep -l blkioLeaf) $ sed -i s/blkioThrottle/throttle/g $(git grep -l blkioThrottle) Signed-off-by: W. Trevor King <wking@tremily.us>
a70bd8f
to
d8ca338
Compare
These are long enough without the prefix, and
linux.resources.blockIO.blkioWeight
, etc. are just as specific aslinux.resources.blockIO.weight
. Generated with:Property-name polishing inspired by #859, in case we want to clean this sort of thing up before 1.0. If not, we can just close this PR.