Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753833AbbHFCap (ORCPT ); Wed, 5 Aug 2015 22:30:45 -0400 Received: from mgwkm01.jp.fujitsu.com ([202.219.69.168]:27572 "EHLO mgwkm01.jp.fujitsu.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752836AbbHFCan (ORCPT ); Wed, 5 Aug 2015 22:30:43 -0400 X-SecurityPolicyCheck: OK by SHieldMailChecker v2.3.2 X-SHieldMailCheckerPolicyVersion: FJ-ISEC-20150223 X-SHieldMailCheckerMailID: b7f00c6c7a0c4e51b0ca9a33506749d2 Subject: Re: [PATCH v2 1/3] cgroup: define controller file conventions To: Michal Hocko References: <1438641689-14655-1-git-send-email-tj@kernel.org> <1438641689-14655-2-git-send-email-tj@kernel.org> <20150804193101.GI17598@mtj.duckdns.org> <55C15B4C.9080202@jp.fujitsu.com> <20150805074758.GA11182@dhcp22.suse.cz> Cc: Tejun Heo , mingo@redhat.com, peterz@infradead.org, hannes@cmpxchg.org, lizefan@huawei.com, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com From: Kamezawa Hiroyuki Message-ID: <55C2C6B0.3080203@jp.fujitsu.com> Date: Thu, 6 Aug 2015 11:30:08 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150805074758.GA11182@dhcp22.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1741 Lines: 54 On 2015/08/05 16:47, Michal Hocko wrote: > On Wed 05-08-15 09:39:40, KAMEZAWA Hiroyuki wrote: > [...] >> so, for memory controller, we'll have > > We currently have only current, low, high, max and events currently. > All other knobs are either deprecated or waiting for a usecase to emerge > before they get added. > Sure. I think following has users. - *.stat - for chekcing health of cgroup ,or for debug - *.pressure_level - for notifying memory pressure - *.swappiness - for adjusting LRU activity per application type. - *.oom_control - for surviving/notifiyng out of memory memcg's oom can be recovered if limit goes up rather than kill. But I know people says this knob is not useful. This will require discussion. Hm. If we don't want to increase files, NETLINK or systemcall is an another choice of subsystem specific interface ? -Kame >> (in alphabet order) >> memory.failcnt >> memory.force_empty (<= should this be removed ?) >> memory.kmem.failcnt >> memory.kmem.max >> memory.kmem.max_usage >> memory.kmem.slabinfo >> memory.kmem.tcp.failcnt >> memory.kmem.tcp.max >> memory.kmem.tcp.max_usage >> memory.kmem.tcp.usage >> memory.kmem.usage >> memory.max >> memory.max_usage >> memory.move_charge_at_immigrate >> memory.numa_stat >> memory.oom_control >> memory.pressure_level >> memory.high >> memory.swapiness >> memory.usage >> memory.use_hierarchy (<= removed) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/