Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751981AbZGOFZd (ORCPT ); Wed, 15 Jul 2009 01:25:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751708AbZGOFZc (ORCPT ); Wed, 15 Jul 2009 01:25:32 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:51057 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbZGOFZc (ORCPT ); Wed, 15 Jul 2009 01:25:32 -0400 Date: Wed, 15 Jul 2009 10:55:25 +0530 From: Balbir Singh To: KAMEZAWA Hiroyuki Cc: Andrew Morton , linux-mm@kvack.org, lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org, KOSAKI Motohiro Subject: Re: [RFC][PATCH 0/5] Memory controller soft limit patches (v9) Message-ID: <20090715052525.GG24034@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com References: <20090710125950.5610.99139.sendpatchset@balbir-laptop> <20090715040811.GF24034@balbir.in.ibm.com> <20090715133324.e4683ef2.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20090715133324.e4683ef2.kamezawa.hiroyu@jp.fujitsu.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1922 Lines: 52 * KAMEZAWA Hiroyuki [2009-07-15 13:33:24]: > On Wed, 15 Jul 2009 09:38:11 +0530 > Balbir Singh wrote: > > > * Balbir Singh [2009-07-10 18:29:50]: > > > > > > > > From: Balbir Singh > > > > > > New Feature: Soft limits for memory resource controller. > > > > > > Here is v9 of the new soft limit implementation. Soft limits is a new feature > > > for the memory resource controller, something similar has existed in the > > > group scheduler in the form of shares. The CPU controllers interpretation > > > of shares is very different though. > > > > > > > If there are no objections to these patches, could we pick them up for > > testing in mmotm. > > > > If any, will be fixed up in mmotm. About behavior, I don't have more things > than I've said. (dealying kswapd is not very good.) > > But plz discuss with Vladislav Buzov about implementation details of [2..3/5]. > == > [PATCH 1/2] Resource usage threshold notification addition to res_counter (v3) > > It seems there are multiple functionalities you can shere with them. > > - hierarchical threshold check > - callback or notify agaisnt threshold. > etc.. > > I'm very happy if all messy things around res_counter+hierarchy are sorted out > before diving into melting pot. I hope both of you have nice interfaces and > keep res_counter neat. > I do see scope for reuse, but I've not yet gotten to reviewing v3 of the patches. I will, I could potentially get him to base his patches on top of this. One of the interesting things that Paul pointed out was of global state. -- Balbir -- 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/