From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: memcg: softlimit on internal nodes Date: Tue, 23 Apr 2013 15:06:27 +0200 Message-ID: <20130423130627.GG8001@dhcp22.suse.cz> References: <20130421022321.GE19097@mtj.dyndns.org> <20130422042445.GA25089@mtj.dyndns.org> <20130422153730.GG18286@dhcp22.suse.cz> <20130422154620.GB12543@htj.dyndns.org> <20130422155454.GH18286@dhcp22.suse.cz> <51765FB2.3070506@parallels.com> <20130423114020.GC8001@dhcp22.suse.cz> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Michel Lespinasse Cc: Glauber Costa , Tejun Heo , Johannes Weiner , Balbir Singh , KAMEZAWA Hiroyuki , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Hugh Dickins , Ying Han , Greg Thelen On Tue 23-04-13 05:51:36, Michel Lespinasse wrote: [...] > The issue I see is that even when people configure soft limits B+C < > A, your current proposal still doesn't "leave the other alone" as > Glauber and I think we should. If B+C < A then B resp. C get reclaimed only if A is over the limit which means that it couldn't reclaimed enough to get bellow the limit when we bang on it before B and C. We can update the implementation later to be more clever in situations like this but this is not that easy because once we get away from the round robin over the tree then we might end up having other issues - like unfairness etc... That's why I wanted to have this as simple as possible. -- Michal Hocko SUSE Labs