[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0910290132320.11476@chino.kir.corp.google.com>
Date: Thu, 29 Oct 2009 01:35:43 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: vedran.furac@...il.com
cc: Hugh Dickins <hugh.dickins@...cali.co.uk>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
minchan.kim@...il.com, Andrew Morton <akpm@...ux-foundation.org>,
Andrea Arcangeli <aarcange@...hat.com>
Subject: Re: Memory overcommit
On Thu, 29 Oct 2009, Vedran Furac wrote:
> > We would know if you posted the data.
>
> I need to find some free time to destroy a session on a computer which I
> use for work. You could easily test it yourself also as this doesn't
> happen only to me.
>
> Anyways, here it is... this time it started with ntpd:
>
> http://pastebin.com/f3f9674a0
>
That oom log shows 12 ooms but no tasks actually appear to be getting
killed (there're no "Killed process 1234 (task)" found). Do you have any
idea why?
Anyway, as I posted in response to KAMEZAWA-san's patch, the change to
get_mm_rss(mm) prefers Xorg more than the current implementation.
>From your log at the link above:
total_vm
669624 test
195695 krunner
187342 krusader
168881 plasma-desktop
130562 ktorrent
127081 knotify4
125881 icedove-bin
123036 akregator
rss
668738 test
42191 Xorg
30761 firefox-bin
13331 icedove-bin
10234 ktorrent
9263 akregator
8864 plasma-desktop
7532 krunner
Can you explain why Xorg is preferred as a baseline to kill rather than
krunner in your example?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists