On 6/15/2016 6:27 AM, Minchan Kim wrote: > > Yeb, I read Johannes's thread which suggests one-cgroup-per-app model. > It does make sense to me. It is worth to try although I guess it's not > easy to control memory usage on demand, not proactively. > If we can do, maybe we don't need per-process reclaim policy which > is rather coarse-grained model of reclaim POV. > However, a concern with one-cgroup-per-app model is LRU list size > of a cgroup is much smaller so how LRU aging works well and > LRU churing(e.g., compaction) effect would be severe than old. And I was thinking what would vmpressure mean and how to use it when cgroup is per task. > > I guess codeaurora tried memcg model for android. > Could you share if you know something? > We tried, but had issues with charge migration and then Johannes suggested per task cgroup. But that's not tried yet.
Thanks