On Wed 15-11-17 11:18:13, Roman Gushchin wrote: > On Wed, Nov 15, 2017 at 09:35:04AM +0100, Michal Hocko wrote: [...] > > So my primary question is, why don't you simply allow hugetlb controller > > rather than tweak stats for memcg? Is there any fundamental reason why > > hugetlb controller is not v2 compatible? > > I really don't know if the hugetlb controller has enough users to deserve > full support in v2 interface: adding knobs like memory.hugetlb.current, > memory.hugetlb.min, memory.hugetlb.high, memory.hugetlb.max, etc. > > I'd be rather conservative here and avoid adding a lot to the interface > without clear demand. Also, hugetlb pages are really special, and it's > at least not obvious how, say, memory.high should work for it. But you clearly want the hugetlb accoutning and that is what hugetlb controller is for. You might not be interested in the limit enforcement but that is not strictly required. So my question remains. Why don't we reuse an existing infrastructure and add a new which might confuse users in an extreme case? Please note that I am not saying your patch is wrong, I just do not see why we should handle hugetlb pages 2 different ways to achieve a common infrastructure. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
