From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751933AbcFPEVw (ORCPT <rfc822;w@1wt.eu>);
	Thu, 16 Jun 2016 00:21:52 -0400
Received: from smtp.codeaurora.org ([198.145.29.96]:59834 "EHLO
	smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750757AbcFPEVu (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 16 Jun 2016 00:21:50 -0400
Subject: Re: [PATCH v1 0/3] per-process reclaim
To: Minchan Kim <minchan@kernel.org>
References: <1465804259-29345-1-git-send-email-minchan@kernel.org>
 <8f2190f4-4388-0eb2-0ffc-b2190280b11a@codeaurora.org>
 <20160615005755.GD17127@bbox>
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>
From: Vinayak Menon <vinmenon@codeaurora.org>
Message-ID: <5e33c94d-d580-2e80-6818-bfb55a9a8a48@codeaurora.org>
Date: Thu, 16 Jun 2016 09:51:41 +0530
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <20160615005755.GD17127@bbox>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


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