From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753699Ab1A1PUI (ORCPT ); Fri, 28 Jan 2011 10:20:08 -0500 Received: from smtp102.prem.mail.ac4.yahoo.com ([76.13.13.41]:29627 "HELO smtp102.prem.mail.ac4.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751731Ab1A1PUG (ORCPT ); Fri, 28 Jan 2011 10:20:06 -0500 X-Yahoo-SMTP: _Dag8S.swBC1p4FJKLCXbs8NQzyse1SYSgnAbY0- X-YMail-OSG: 4MA1VeUVM1nIndq4IS1Uq2F7wDQlq_Hkmuu41b4OxizpeHg c14niju3qvplLMcR53eZicRIdYXwShwP8HzetsL7f81sMsgPhonAdI_P4OR1 v8efhVrTekD0fEbUpbYy7I85P7Zqy7ZL2C3yqt8O9c0Wjg7hM7ANDKPbaOYn xau9ooPIKZDar5KOZWMBucI5xcSAtjcZgw7ZtXhbpJLJoNrR7HWmYBxKKZkh vbqRwHMMaZ0M- X-Yahoo-Newman-Property: ymail-3 Date: Fri, 28 Jan 2011 09:20:02 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@router.home To: KAMEZAWA Hiroyuki cc: Minchan Kim , balbir@linux.vnet.ibm.com, linux-mm@kvack.org, akpm@linux-foundation.org, npiggin@kernel.dk, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, kosaki.motohiro@jp.fujitsu.com Subject: Re: [PATCH 3/3] Provide control over unmapped pages (v4) In-Reply-To: <20110128165605.3cbe5208.kamezawa.hiroyu@jp.fujitsu.com> Message-ID: References: <20110125051003.13762.35120.stgit@localhost6.localdomain6> <20110125051015.13762.13429.stgit@localhost6.localdomain6> <20110128064851.GB5054@balbir.in.ibm.com> <20110128165605.3cbe5208.kamezawa.hiroyu@jp.fujitsu.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 28 Jan 2011, KAMEZAWA Hiroyuki wrote: > > > I see it as a tradeoff of when to check? add_to_page_cache or when we > > > are want more free memory (due to allocation). It is OK to wakeup > > > kswapd while allocating memory, somehow for this purpose (global page > > > cache), add_to_page_cache or add_to_page_cache_locked does not seem > > > the right place to hook into. I'd be open to comments/suggestions > > > though from others as well. > > I don't like add hook here. > AND I don't want to run kswapd because 'kswapd' has been a sign as > there are memory shortage. (reusing code is ok.) > > How about adding new daemon ? Recently, khugepaged, ksmd works for > managing memory. Adding one more daemon for special purpose is not > very bad, I think. Then, you can do > - wake up without hook > - throttle its work. > - balance the whole system rather than zone. > I think per-node balance is enough... I think we already have enough kernel daemons floating around. They are multiplying in an amazing way. What would be useful is to map all the memory management background stuff into a process. May call this memd instead? Perhaps we can fold khugepaged into kswapd as well etc.