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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
