From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with SMTP id 5F8FA6B00C9 for ; Mon, 2 Mar 2009 01:22:47 -0500 (EST) Received: from mt1.gw.fujitsu.co.jp ([10.0.50.74]) by fgwmail7.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id n226Mjmv026320 for (envelope-from kamezawa.hiroyu@jp.fujitsu.com); Mon, 2 Mar 2009 15:22:45 +0900 Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id D3DF145DE50 for ; Mon, 2 Mar 2009 15:22:44 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id A769145DE4E for ; Mon, 2 Mar 2009 15:22:44 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 791B61DB803B for ; Mon, 2 Mar 2009 15:22:44 +0900 (JST) Received: from m107.s.css.fujitsu.com (m107.s.css.fujitsu.com [10.249.87.107]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 26C781DB803A for ; Mon, 2 Mar 2009 15:22:44 +0900 (JST) Date: Mon, 2 Mar 2009 15:21:28 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [PATCH 0/4] Memory controller soft limit patches (v3) Message-Id: <20090302152128.e74f51ef.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20090302060519.GG11421@balbir.in.ibm.com> References: <20090301062959.31557.31079.sendpatchset@localhost.localdomain> <20090302092404.1439d2a6.kamezawa.hiroyu@jp.fujitsu.com> <20090302044043.GC11421@balbir.in.ibm.com> <20090302143250.f47758f9.kamezawa.hiroyu@jp.fujitsu.com> <20090302060519.GG11421@balbir.in.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: balbir@linux.vnet.ibm.com Cc: linux-mm@kvack.org, Sudhir Kumar , YAMAMOTO Takashi , Bharata B Rao , Paul Menage , lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org, KOSAKI Motohiro , David Rientjes , Pavel Emelianov , Dhaval Giani , Rik van Riel , Andrew Morton List-ID: On Mon, 2 Mar 2009 11:35:19 +0530 Balbir Singh wrote: > * KAMEZAWA Hiroyuki [2009-03-02 14:32:50]: > > > On Mon, 2 Mar 2009 10:10:43 +0530 > > Balbir Singh wrote: > > > > > * KAMEZAWA Hiroyuki [2009-03-02 09:24:04]: > > > > > > > On Sun, 01 Mar 2009 11:59:59 +0530 > > > > Balbir Singh wrote: > > > > > > > > > > > > > > From: Balbir Singh > > > > > > > > > > At first, it's said "When cgroup people adds something, the kernel gets slow". > > > > This is my start point of reviewing. Below is comments to this version of patch. > > > > > > > > 1. I think it's bad to add more hooks to res_counter. It's enough slow to give up > > > > adding more fancy things.. > > > > > > res_counters was desgined to be extensible, why is adding anything to > > > it going to make it slow, unless we turn on soft_limits? > > > > > You inserted new "if" logic in the core loop. > > (What I want to say here is not that this is definitely bad but that "isn't there > > any alternatives which is less overhead.) > > > > > > > > > > > > 2. please avoid to add hooks to hot-path. In your patch, especially a hook to > > > > mem_cgroup_uncharge_common() is annoying me. > > > > > > If soft limits are not enabled, the function does a small check and > > > leaves. > > > > > &soft_fail_res is passed always even if memory.soft_limit==ULONG_MAX > > res_counter_soft_limit_excess() adds one more function call and spinlock, and irq-off. > > > > OK, I see that overhead.. I'll figure out a way to work around it. > > > > > > > > > 3. please avoid to use global spinlock more. > > > > no lock is best. mutex is better, maybe. > > > > > > > > > > No lock to update a tree which is update concurrently? > > > > > Using tree/sort itself is nonsense, I believe. > > > > I tried using prio trees in the past, but they are not easy to update > either. I won't mind asking for suggestions for a data structure that > can scaled well, allow quick insert/delete and search. > Now, because the routine is called by kswapd() not by try_to_free..... It's not necessary to be very very fast. That's my point. Thanks, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org