linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Chris Friesen <cfriesen@nortel.com>,
	Rik van Riel <riel@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: tracking memory usage/leak in "inactive" field in /proc/meminfo?
Date: Wed, 10 Feb 2010 09:20:52 +0530	[thread overview]
Message-ID: <20100210035052.GH3290@balbir.in.ibm.com> (raw)
In-Reply-To: <20100210093140.12D9.A69D9226@jp.fujitsu.com>

* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> [2010-02-10 09:32:07]:

> > Hi,
> > 
> > I'm hoping you can help me out.  I'm on a 2.6.27 x86 system and I'm
> > seeing the "inactive" field in /proc/meminfo slowly growing over time to
> > the point where eventually the oom-killer kicks in and starts killing
> > things.  The growth is not evident in any other field in /proc/meminfo.
> > 
> > I'm trying to figure out where the memory is going, and what it's being
> > used for.
> > 
> > As I've found, the fields in /proc/meminfo don't add up...in particular,
> > active+inactive is quite a bit larger than
> > buffers+cached+dirty+anonpages+mapped+pagetables+vmallocused.  Initially
> > the difference is about 156MB, but after about 13 hrs the difference is
> > 240MB.
> > 
> > How can I track down where this is going?  Can you suggest any
> > instrumentation that I can add?
> > 
> > I'm reasonably capable, but I'm getting seriously confused trying to
> > sort out the memory subsystem.  Some pointers would be appreciated.
> 
> can you please post your /proc/meminfo?
>

Do you have swap enabled? Can you help with the OOM killed dmesg log?
Does the situation get better after OOM killing. /proc/meminfo as
Kosaki suggested would be important as well. 

-- 
	Three Cheers,
	Balbir

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-02-10  3:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 16:51 tracking memory usage/leak in "inactive" field in /proc/meminfo? Chris Friesen
2010-02-10  0:32 ` KOSAKI Motohiro
2010-02-10  3:50   ` Balbir Singh [this message]
2010-02-10  4:09     ` KOSAKI Motohiro
2010-02-10 17:05   ` Chris Friesen
2010-02-11  0:45     ` Minchan Kim
2010-02-11 18:54       ` Chris Friesen
2010-02-11 19:04         ` Rik van Riel
2010-02-12  2:38         ` Minchan Kim
2010-02-12  7:35           ` Chris Friesen
2010-02-12  8:04             ` KOSAKI Motohiro
2010-02-15 15:50             ` Chris Friesen
2010-02-15 17:00               ` Rik van Riel
2010-02-16 16:52                 ` Chris Friesen
2010-02-16 17:12                   ` Rik van Riel
2010-02-16 21:26                     ` Chris Friesen
2010-02-16 22:22                       ` Rik van Riel
2010-02-18 15:39                         ` tracking memory usage/leak in "inactive" field in /proc/meminfo? -- solved Chris Friesen
2010-02-12 17:50           ` tracking memory usage/leak in "inactive" field in /proc/meminfo? Catalin Marinas
2010-02-13  6:29     ` Balbir Singh
2010-02-15 16:02       ` Chris Friesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100210035052.GH3290@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=cfriesen@nortel.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).