-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Unify behavior for memory cgroup #343
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
Unify behavior for memory cgroup #343
Conversation
We have a rule that for optional cgroups, don't fail if some of them are not mounted, but we want it fail hard when a user specifies an option and we are unable to fulfill the request. Memory cgroup should also follow this rule. Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
|
@rajasec This new change still includes that fix, in another way. If memory cgroup is not mounted and user is not using memory options, it won't fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hqhq
if memory subsystem is not mounted, empty path is passed in set interface ? is that correct ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's intended, so that we can get error in writeFile function.
|
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hqhq
if path not equal to empty( which means path exists), code is creating mkdir again with "path"
is that intentional ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How "again"? It's the first time we create "path".
|
@hqhq |
|
LGTM |
Unify behavior for memory cgroup
…ormance Improve json encoding performance for specs-go
Through 6734c7a (Merge pull request opencontainers#370 from vbatts/json_schema_and_examples, 2016-04-11). The only unlisted changes to master were a brief run with ffjson (opencontainers#343, opencontainers#351), but that was pulled out due to gccgo issues in opencontainers#363. Signed-off-by: W. Trevor King <wking@tremily.us>
We have a rule that for optional cgroups, don't fail if some
of them are not mounted, but we want it fail hard when a
user specifies an option and we are unable to fulfill the
request.
Memory cgroup should also follow this rule.
Signed-off-by: Qiang Huang h.huangqiang@huawei.com