Re: [PATCH] memcg: Ignore unprotected parent in mem_cgroup_protected()

Hi Chris, On 2019/6/16 PM 6:37, Chris Down wrote: > Hi Xunlei, > > Xunlei Pang writes: >> docker and various types(different memory capacity) of containers >> are managed by k8s, it's a burden for k8s to maintain those dynamic >> figures, simply set "max" to key containers is always welcome. >

Re: [PATCH] memcg: Ignore unprotected parent in mem_cgroup_protected()

Hi Xunlei, Xunlei Pang writes: docker and various types(different memory capacity) of containers are managed by k8s, it's a burden for k8s to maintain those dynamic figures, simply set "max" to key containers is always welcome. Right, setting "max" is generally a fine way of going about it.

Re: [PATCH] memcg: Ignore unprotected parent in mem_cgroup_protected()

Hi Chirs, On 2019/6/16 AM 12:08, Chris Down wrote: > Hi Xunlei, > > Xunlei Pang writes: >> Currently memory.min|low implementation requires the whole >> hierarchy has the settings, otherwise the protection will >> be broken. >> >> Our hierarchy is kind of like(memory.min value in brackets), >>

Re: [PATCH] memcg: Ignore unprotected parent in mem_cgroup_protected()

Hi Xunlei, Xunlei Pang writes: Currently memory.min|low implementation requires the whole hierarchy has the settings, otherwise the protection will be broken. Our hierarchy is kind of like(memory.min value in brackets), root | docker(0) /

[PATCH] memcg: Ignore unprotected parent in mem_cgroup_protected()

Currently memory.min|low implementation requires the whole hierarchy has the settings, otherwise the protection will be broken. Our hierarchy is kind of like(memory.min value in brackets), root | docker(0) /\ c1(max) c2(0)