|
Description
|
While thinking of the administrative model for the setting CPU caps for a project/zone I noticed that the current prctl model is confuding.
1) There is no way to say "set this rctl to its default value".
2) There is no way of telling that somevalue is having the default value
3) The only way to specify the default value in /etc/project file is to omit the resource
4) There is no sane way to set value to infinity
5) prctl -r doesn't work if the value is not created in the first place. As a result, to
set a zone cap the user should do prctl -c the first time. Then, to change the value,
prctl -r should be used and after caps are disabled with -n, -c should be used again.
So the following implrovements are suggested:
1) prctl -r should be smart and insert the value if it is not present
2) Support the "default" token as the resource value for prctl
3) Support the "default" token as possible value in project(4)
4) Have prctl print default values as "default"
5) Provide ways to query default rctl values
6) Allow "infinity" token as the resource value.
|
