Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755027Ab1EQN4I (ORCPT ); Tue, 17 May 2011 09:56:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:6610 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754786Ab1EQN4G (ORCPT ); Tue, 17 May 2011 09:56:06 -0400 Message-ID: <4DD27E62.50806@redhat.com> Date: Tue, 17 May 2011 09:55:46 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.38.b3pre.fc13 Lightning/1.0b3pre Thunderbird/3.1.9 MIME-Version: 1.0 To: Johannes Weiner CC: Ying Han , KAMEZAWA Hiroyuki , Daisuke Nishimura , Balbir Singh , Michal Hocko , Andrew Morton , Minchan Kim , KOSAKI Motohiro , Mel Gorman , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [rfc patch 4/6] memcg: reclaim statistics References: <1305212038-15445-1-git-send-email-hannes@cmpxchg.org> <1305212038-15445-5-git-send-email-hannes@cmpxchg.org> <20110516231028.GV16531@cmpxchg.org> <20110517074230.GY16531@cmpxchg.org> In-Reply-To: <20110517074230.GY16531@cmpxchg.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1511 Lines: 41 On 05/17/2011 03:42 AM, Johannes Weiner wrote: > It does hierarchical soft limit reclaim once triggered, but I meant > that soft limits themselves have no hierarchical meaning. Say you > have the following hierarchy: > > root_mem_cgroup > > aaa bbb > > a1 a2 b1 b2 > > a1-1 > > Consider aaa and a1 had a soft limit. If global memory arose, aaa and > all its children would be pushed back with the current scheme, the one > you are proposing, and the one I am proposing. > > But now consider aaa hitting its hard limit. Regular target reclaim > will be triggered, and a1, a2, and a1-1 will be scanned equally from > hierarchical reclaim. That a1 is in excess of its soft limit is not > considered at all. > > With what I am proposing, a1 and a1-1 would be pushed back more > aggressively than a2, because a1 is in excess of its soft limit and > a1-1 is contributing to that. Ying, I think Johannes has a good point. I do not see a way to enforce the limits properly with the scheme we came up with at LSF, in the hierarchical scenario above. There may be a way, but until we think of it, I suspect it will be better to go with Johannes's scheme for now. -- All rights reversed -- 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/