[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091218083348.c75dbb81.kamezawa.hiroyu@jp.fujitsu.com>
Date: Fri, 18 Dec 2009 08:33:48 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: David Rientjes <rientjes@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Daisuke Nishimura <nishimura@....nes.nec.co.jp>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Christoph Lameter <cl@...ux-foundation.org>
Subject: Re: [BUGFIX][PATCH] oom-kill: fix NUMA consraint check with
nodemask v4.2
On Thu, 17 Dec 2009 14:23:39 -0800 (PST)
David Rientjes <rientjes@...gle.com> wrote:
> On Tue, 15 Dec 2009, KAMEZAWA Hiroyuki wrote:
>
> > What I can't undestand is the technique to know whether a (unknown) process is
> > leaking memory or not by checking vm_size.
>
> Memory leaks are better identified via total_vm since leaked memory has a
> lower probability of staying resident in physical memory.
>
Because malloc() writes header on newly allcoated memory, (vm_size - rss) cannot
be far from a some important program which wakes up once in a
day or sleep in the day works in the night.
I hope user knows expected memory size of applications, but I know it can't.
Sigh...
Thanks,
-Kame
--
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