From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 5084A6B0089 for ; Tue, 7 Dec 2010 01:15:10 -0500 (EST) Received: from d23relay05.au.ibm.com (d23relay05.au.ibm.com [202.81.31.247]) by e23smtp08.au.ibm.com (8.14.4/8.13.1) with ESMTP id oB76F61w026837 for ; Tue, 7 Dec 2010 17:15:06 +1100 Received: from d23av01.au.ibm.com (d23av01.au.ibm.com [9.190.234.96]) by d23relay05.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oB76F5lB1732850 for ; Tue, 7 Dec 2010 17:15:05 +1100 Received: from d23av01.au.ibm.com (loopback [127.0.0.1]) by d23av01.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oB76F4KJ006839 for ; Tue, 7 Dec 2010 17:15:05 +1100 Date: Tue, 7 Dec 2010 11:45:03 +0530 From: Balbir Singh Subject: Re: [PATCH 1/4] Add kswapd descriptor. Message-ID: <20101207061503.GH3158@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com References: <1291099785-5433-1-git-send-email-yinghan@google.com> <1291099785-5433-2-git-send-email-yinghan@google.com> <20101130160838.4c66febf.kamezawa.hiroyu@jp.fujitsu.com> <20101130172710.38de418b.kamezawa.hiroyu@jp.fujitsu.com> <20101130175443.f01f4d09.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20101130175443.f01f4d09.kamezawa.hiroyu@jp.fujitsu.com> Sender: owner-linux-mm@kvack.org To: KAMEZAWA Hiroyuki Cc: Minchan Kim , Ying Han , Daisuke Nishimura , Andrew Morton , Mel Gorman , Johannes Weiner , Christoph Lameter , Wu Fengguang , Andi Kleen , Hugh Dickins , Rik van Riel , KOSAKI Motohiro , Tejun Heo , linux-mm@kvack.org List-ID: * KAMEZAWA Hiroyuki [2010-11-30 17:54:43]: > On Tue, 30 Nov 2010 17:27:10 +0900 > KAMEZAWA Hiroyuki wrote: > > > On Tue, 30 Nov 2010 17:15:37 +0900 > > Minchan Kim wrote: > > > > > Ideally, I hope we unify global and memcg of kswapd for easy > > > maintainance if it's not a big problem. > > > When we make patches about lru pages, we always have to consider what > > > I should do for memcg. > > > And when we review patches, we also should consider what the patch is > > > missing for memcg. > > > It makes maintainance cost big. Of course, if memcg maintainers is > > > involved with all patches, it's no problem as it is. > > > > > I know it's not. But thread control of kswapd will not have much merging point. > > And balance_pgdat() is fully replaced in patch/3. The effort for merging seems > > not big. > > > > kswapd's balance_pgdat() is for following > - reclaim pages within a node. > - balancing zones in a pgdat. > > memcg's background reclaim needs followings. > - reclaim pages within a memcg > - reclaim pages from arbitrary zones, if it's fair, it's good. > But it's not important from which zone the pages are reclaimed from. > (I'm not sure we can select "the oldest" pages from divided LRU.) > Yes, if it is fair, then we don't break what kswapd tries to do, so fairness is quite important, in that we don't leaves zones unbalanced (at least by very much) as we try to do background reclaim. But sometimes it cannot be helped, specially if there are policies that bias the allocation. > Then, merging will put 2 _very_ different functionalities into 1 function. > > So, I thought it's simpler to implement > > 1. a victim node selector (This algorithm will never be in kswapd.) A victim node selector per memcg? Could you clarify the context of node here? > 2. call _existing_ try_to_free_pages_mem_cgroup() with node local zonelist. > Sharing is enough. > > kswapd stop/go routine may be able to be shared. But this patch itself seems not > very good to me. > > Thanks, > -Kame > -- Three Cheers, Balbir -- 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/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org