From: Vinayak Menon <vinmenon@codeaurora.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Rik van Riel <riel@redhat.com>, Redmond <u93410091@gmail.com>,
"ZhaoJunmin Zhao(Junmin)" <zhaojunmin@huawei.com>,
Juneho Choi <juno.choi@lge.com>,
Sangwoo Park <sangwoo2.park@lge.com>,
Chan Gyun Jeong <chan.jeong@lge.com>
Subject: Re: [PATCH v1 0/3] per-process reclaim
Date: Thu, 16 Jun 2016 09:51:41 +0530 [thread overview]
Message-ID: <5e33c94d-d580-2e80-6818-bfb55a9a8a48@codeaurora.org> (raw)
In-Reply-To: <20160615005755.GD17127@bbox>
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
prev parent reply other threads:[~2016-06-16 4:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 7:50 [PATCH v1 0/3] per-process reclaim Minchan Kim
2016-06-13 7:50 ` [PATCH v1 1/3] mm: vmscan: refactoring force_reclaim Minchan Kim
2016-06-13 7:50 ` [PATCH v1 2/3] mm: vmscan: shrink_page_list with multiple zones Minchan Kim
2016-06-13 7:50 ` [PATCH v1 3/3] mm: per-process reclaim Minchan Kim
2016-06-13 15:06 ` Johannes Weiner
2016-06-15 0:40 ` Minchan Kim
2016-06-16 11:07 ` Michal Hocko
2016-06-16 14:41 ` Johannes Weiner
2016-06-17 6:43 ` Minchan Kim
2016-06-17 7:24 ` Balbir Singh
2016-06-17 7:57 ` Vinayak Menon
2016-06-13 17:06 ` Rik van Riel
2016-06-15 1:01 ` Minchan Kim
2016-06-13 11:50 ` [PATCH v1 0/3] " Chen Feng
2016-06-13 12:22 ` ZhaoJunmin Zhao(Junmin)
2016-06-15 0:43 ` Minchan Kim
2016-06-13 13:29 ` Vinayak Menon
2016-06-15 0:57 ` Minchan Kim
2016-06-16 4:21 ` Vinayak Menon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e33c94d-d580-2e80-6818-bfb55a9a8a48@codeaurora.org \
--to=vinmenon@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=chan.jeong@lge.com \
--cc=juno.choi@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=sangwoo2.park@lge.com \
--cc=u93410091@gmail.com \
--cc=zhaojunmin@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).