Skip to content

Conversation

@hqhq
Copy link
Contributor

@hqhq hqhq commented Oct 20, 2015

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

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
Copy link
Contributor

rajasec commented Oct 20, 2015

@hqhq
Earlier there was fix which was committed for memory.go via #118 to runc
is that becomes invalid now with your new changes

@hqhq
Copy link
Contributor Author

hqhq commented Oct 20, 2015

@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.

Copy link
Contributor

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 ?

Copy link
Contributor Author

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.

@crosbymichael
Copy link
Member

LGTM

Copy link
Contributor

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 ?

Copy link
Contributor Author

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".

@rajasec
Copy link
Contributor

rajasec commented Oct 26, 2015

@hqhq
You are right. Thanks.

@mrunalp
Copy link
Contributor

mrunalp commented Nov 2, 2015

LGTM

mrunalp pushed a commit that referenced this pull request Nov 2, 2015
@mrunalp mrunalp merged commit cf73b32 into opencontainers:master Nov 2, 2015
@hqhq hqhq deleted the hq_unify_behavior_for_memory branch November 3, 2015 01:47
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
…ormance

Improve json encoding performance for specs-go
stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants