Skip to content
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: Add Memory cgroup's use_hierarchy #985

Merged
merged 1 commit into from
Dec 17, 2019

Conversation

BooleanCat
Copy link

Addresses issue #984

Signed-off-by: Tom Godkin thgodkin@gmail.com
Co-authored-by: Claudia Beresford cberesford@pivotal.io

@BooleanCat
Copy link
Author

BooleanCat commented Aug 21, 2018

@crosbymichael Is the Signed-off-by check sensitive to its position in the commit message maybe? I do have it but it's before a Co-authored-by.

I swapped the order and force pushed but it doesn't seem to have poked the mechanism to try again.

@crosbymichael
Copy link
Member

Not sure. Maybe it wants both to be signed off

Co-authored-by: Claudia Beresford <cberesford@pivotal.io>
Signed-off-by: Danail Branekov <danailster@gmail.com>
@crosbymichael
Copy link
Member

crosbymichael commented Aug 22, 2018

LGTM

Approved with PullApprove

@BooleanCat
Copy link
Author

Bump, seems like we another LGTM to get this merged. Once it's in we can work on getting runc to do something with this property.

@vbatts
Copy link
Member

vbatts commented Sep 11, 2018

this doesn't just apply to cgroups v2? perhaps that ought to be clarified that it's for propagating to nested/child groups, regardless to using cgroups of v2.

@vbatts
Copy link
Member

vbatts commented Dec 17, 2019

house keeping: this is an OPTIONAL feature, so non-breaking forward compatible.

LGTM

Approved with PullApprove

@vbatts vbatts merged commit 8b180f3 into opencontainers:master Dec 17, 2019
@vbatts vbatts mentioned this pull request Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants