From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757460Ab2ATA0N (ORCPT ); Thu, 19 Jan 2012 19:26:13 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:45116 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756222Ab2ATA0K (ORCPT ); Thu, 19 Jan 2012 19:26:10 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Fri, 20 Jan 2012 09:24:49 +0900 From: KAMEZAWA Hiroyuki To: Rik van Riel Cc: Minchan Kim , linux-mm , LKML , leonid.moiseichuk@nokia.com, penberg@kernel.org, mel@csn.ul.ie, rientjes@google.com, KOSAKI Motohiro , Johannes Weiner , Marcelo Tosatti , Andrew Morton , Ronen Hod Subject: Re: [RFC 2/3] vmscan hook Message-Id: <20120120092449.4ecbec86.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <4F182BF3.7050809@redhat.com> References: <1326788038-29141-1-git-send-email-minchan@kernel.org> <1326788038-29141-3-git-send-email-minchan@kernel.org> <20120117173932.1c058ba4.kamezawa.hiroyu@jp.fujitsu.com> <20120117091356.GA29736@barrios-desktop.redhat.com> <20120117190512.047d3a03.kamezawa.hiroyu@jp.fujitsu.com> <20120117230801.GA903@barrios-desktop.redhat.com> <20120118091824.0bde46f7.kamezawa.hiroyu@jp.fujitsu.com> <4F16D46D.5080000@redhat.com> <20120119112528.eda78467.kamezawa.hiroyu@jp.fujitsu.com> <4F182BF3.7050809@redhat.com> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 3.1.1 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 19 Jan 2012 09:42:59 -0500 Rik van Riel wrote: > On 01/18/2012 09:25 PM, KAMEZAWA Hiroyuki wrote: > > On Wed, 18 Jan 2012 09:17:17 -0500 > > Rik van Riel wrote: > > > >> On 01/17/2012 07:18 PM, KAMEZAWA Hiroyuki wrote: > >>> On Wed, 18 Jan 2012 08:08:01 +0900 > >>> Minchan Kim wrote: > >>> > >>>>>>> 2. can't we measure page-in/page-out distance by recording something ? > >>>>>> > >>>>>> I can't understand your point. What's relation does it with swapout prevent? > >>>>>> > >>>>> > >>>>> If distance between pageout -> pagein is short, it means thrashing. > >>>>> For example, recoding the timestamp when the page(mapping, index) was > >>>>> paged-out, and check it at page-in. > >>>> > >>>> Our goal is prevent swapout. When we found thrashing, it's too late. > >>> > >>> If you want to prevent swap-out, don't swapon any. That's all. > >>> Then, you can check the number of FILE_CACHE and have threshold. > >> > >> I think you are getting hung up on a word here. > >> > >> As I understand it, the goal is to push out the point where > >> we start doing heavier swap IO, allowing us to overcommit > >> memory more heavily before things start really slowing down. > >> > > > > Yes. > > > > Hmm, considering that the issue is slow down, > > > > time values as > > > > - 'cpu time used for memory reclaim' > > - 'latency of page allocation' > > - 'application execution speed' ? > > > > may be a better score to see rather than just seeing lru's stat. > > I believe those all qualify as "too late". > > We want to prevent things from becoming bad, for as long > as we (easily) can. > Hmm, then some threshold-notifier interface will be required. Problem is how to know free + page_can_be_freed_without_risk. Thanks, -Kame