From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932109Ab3AIWVw (ORCPT ); Wed, 9 Jan 2013 17:21:52 -0500 Received: from mail-pb0-f53.google.com ([209.85.160.53]:47458 "EHLO mail-pb0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757450Ab3AIWVv (ORCPT ); Wed, 9 Jan 2013 17:21:51 -0500 Date: Wed, 9 Jan 2013 14:21:44 -0800 From: Tejun Heo To: Anton Vorontsov Cc: Glauber Costa , David Rientjes , Pekka Enberg , Mel Gorman , Michal Hocko , "Kirill A. Shutemov" , Luiz Capitulino , Andrew Morton , Greg Thelen , Leonid Moiseichuk , KOSAKI Motohiro , Minchan Kim , Bartlomiej Zolnierkiewicz , John Stultz , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org, patches@linaro.org, kernel-team@android.com, KAMEZAWA Hiroyuki Subject: Re: [PATCH 1/2] Add mempressure cgroup Message-ID: <20130109222144.GF20454@htj.dyndns.org> References: <20130104082751.GA22227@lizard.gateway.2wire.net> <1357288152-23625-1-git-send-email-anton.vorontsov@linaro.org> <20130109203731.GA20454@htj.dyndns.org> <50EDDF1E.6010705@parallels.com> <20130109213604.GA9475@lizard.fhda.edu> <20130109215514.GD20454@htj.dyndns.org> <20130109220641.GA12865@lizard.fhda.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130109220641.GA12865@lizard.fhda.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Anton. On Wed, Jan 09, 2013 at 02:06:41PM -0800, Anton Vorontsov wrote: > Yeah. I started answering your comments about hierarchical accounting, > looked into the memcg code, and realized that *this* is where I need the > memcg stuff. :) Yay, I wasn't completely clueless. > Thus yes, I guess I'll have to integrate it with memcg, or sort of. I really don't know much about memcg internals but I guess implementation can be split into two pieces. memcg already has its own accounting and pressure mechanism so it should be possible to bolt on the mempressure interface on top of already existing data. You can improve / bring some sanity :) to memcg if the proposed mempressure implementation is better. Thanks. -- tejun