Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757000AbZJ1Aez (ORCPT ); Tue, 27 Oct 2009 20:34:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756968AbZJ1Aey (ORCPT ); Tue, 27 Oct 2009 20:34:54 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:44312 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756951AbZJ1Aey (ORCPT ); Tue, 27 Oct 2009 20:34:54 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Wed, 28 Oct 2009 09:32:26 +0900 From: KAMEZAWA Hiroyuki To: Andrea Arcangeli Cc: Hugh Dickins , Minchan Kim , KOSAKI Motohiro , vedran.furac@gmail.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, rientjes@google.com Subject: Re: [RFC][PATCH] oom_kill: avoid depends on total_vm and use real RSS/swap value for oom_score (Re: Memory overcommit Message-Id: <20091028093226.034d2e51.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20091027184743.GD5753@random.random> References: <4ADE3121.6090407@gmail.com> <20091026105509.f08eb6a3.kamezawa.hiroyu@jp.fujitsu.com> <4AE5CB4E.4090504@gmail.com> <20091027122213.f3d582b2.kamezawa.hiroyu@jp.fujitsu.com> <2f11576a0910262310g7aea23c0n9bfc84c900879d45@mail.gmail.com> <20091027153429.b36866c4.minchan.kim@barrios-desktop> <20091027153626.c5a4b5be.kamezawa.hiroyu@jp.fujitsu.com> <28c262360910262355p3cac5c1bla4de9d42ea67fb4e@mail.gmail.com> <20091027164526.da6a23cb.kamezawa.hiroyu@jp.fujitsu.com> <20091027184743.GD5753@random.random> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.5.0 (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 Content-Length: 1394 Lines: 35 On Tue, 27 Oct 2009 19:47:43 +0100 Andrea Arcangeli wrote: > > should be included along with rss isn't quite clear to me: I'm not > > saying you're wrong, not at all, just that it's not quite obvious. > > Agreed it's not obvious. Intuitively I think only including RSS and no > swap is best, but clearly I can't be entirely against including swap > too as there may be scenarios where including swap provides for a > better choice. > > My argument for not including swap is that we kill tasks to free RAM > (we don't really care to free swap, system needs RAM at oom time). > Freeing swap won't immediately help because no RAM is freed when swap > is released (sure other tasks that sits huge in RAM can be moved to > swap after swap isn't full but if we immediately killed those tasks > that were huge in RAM in the first place we'd be better off). > Okay. As first step, I'll divide this into - replace total_vm with anon_rss/file_rss patch - swap accounting - a patch for consider whether swap amount should be included or not. Then, necessary part will go early. And backport will be easy. Thanks, -Kame -- 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/