Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754462AbZJ1UKr (ORCPT ); Wed, 28 Oct 2009 16:10:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754081AbZJ1UKr (ORCPT ); Wed, 28 Oct 2009 16:10:47 -0400 Received: from smtp-out.google.com ([216.239.45.13]:46859 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753102AbZJ1UKq (ORCPT ); Wed, 28 Oct 2009 16:10:46 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:user-agent:mime-version:content-type:x-system-of-record; b=ASw00L+gZgPKrfJLZor1+rsoGm2AQhj+0tQpqlIkexVBXWEnpEFVm9nvBf0cw2o/z ELwXTKEuB6IpuATWDY7lA== Date: Wed, 28 Oct 2009 13:10:43 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Vedran Furac cc: Hugh Dickins , KAMEZAWA Hiroyuki , linux-mm@kvack.org, linux-kernel@vger.kernel.org, KOSAKI Motohiro , minchan.kim@gmail.com, Andrew Morton , Andrea Arcangeli Subject: Re: Memory overcommit In-Reply-To: <4AE846E8.1070303@gmail.com> Message-ID: References: <20091013120840.a844052d.kamezawa.hiroyu@jp.fujitsu.com> <20091014135119.e1baa07f.kamezawa.hiroyu@jp.fujitsu.com> <4ADE3121.6090407@gmail.com> <20091026105509.f08eb6a3.kamezawa.hiroyu@jp.fujitsu.com> <4AE5CB4E.4090504@gmail.com> <20091027122213.f3d582b2.kamezawa.hiroyu@jp.fujitsu.com> <4AE78B8F.9050201@gmail.com> <4AE792B8.5020806@gmail.com> <4AE846E8.1070303@gmail.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1485 Lines: 35 On Wed, 28 Oct 2009, Vedran Furac wrote: > > Those are practically happening simultaneously with very little memory > > being available between each oom kill. Only later is "test" killed: > > > > [97240.203228] Out of memory: kill process 5005 (test) score 256912 or a child > > [97240.206832] Killed process 5005 (test) > > > > Notice how the badness score is less than 1/4th of the others. So while > > you may find it to be hogging a lot of memory, there were others that > > consumed much more. > ^^^^^^^^^^^^^^^^^^^^^ > > This is just wrong. I have 3.5GB of RAM, free says that 2GB are empty > (ignoring cache). Culprit then allocates all free memory (2GB). That > means it is using *more* than all other processes *together*. There > cannot be any other "that consumed much more". > Just post the oom killer results after using echo 1 > /proc/sys/vm/oom_dump_tasks as requested and it will clarify why those tasks were chosen to kill. It will also show the result of using rss instead of total_vm and allow us to see how such a change would have changed the killing order for your workload. > Thanks, I'll try that... but I guess that using rss would yield better > results. > We would know if you posted the data. -- 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/