From: CaT <cat@zip.com.au>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc7: memory leak?
Date: Thu, 17 Jan 2008 23:35:32 +1100 [thread overview]
Message-ID: <20080117123532.GU3940@zip.com.au> (raw)
In-Reply-To: <20080117212142.11EC.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Thu, Jan 17, 2008 at 09:22:50PM +0900, KOSAKI Motohiro wrote:
> Hi
>
> > > > Should all this cache usage not be counted towards the
> > > > 'Cached' entry in meminfo rather then getting counted as part of used
> > > > ram.
> > >
> > > Cached is only the page-cache, not all the other caches we have..
> > > This someones confuses people, but one gets used to it. slabinfo allows
> > > one to easily view others.
> >
> > So what would I have to do to find out the real amount of memory free?
> > Would that be the MemFree field in /proc/meminfo plus, from
> > /proc/slabinfo, *_cache and size-*?
>
> SReclaimable field can't fill requilrement? :)
Ah. Hmm. *pokes about* That does seem to correspond pretty closely to
what happens with the echo 3 >/proc/.... Though it never seems to get to
0 (~4 meg is as close as it gets on this box) which seems to jive with
what Peter said in the other email.
Hmm. I think tomorrow I'll be writing free.pl and modifying my graphing
and monitoring stuff to take this into account somehow. :)
Thanks!
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
prev parent reply other threads:[~2008-01-17 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 6:34 2.6.24-rc7: memory leak? CaT
2008-01-17 11:21 ` Pekka Enberg
2008-01-17 11:22 ` Peter Zijlstra
2008-01-17 11:40 ` CaT
2008-01-17 12:07 ` Peter Zijlstra
2008-01-17 12:14 ` CaT
2008-01-17 12:21 ` Peter Zijlstra
2008-01-17 12:28 ` CaT
2008-01-17 12:22 ` KOSAKI Motohiro
2008-01-17 12:35 ` CaT [this message]
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=20080117123532.GU3940@zip.com.au \
--to=cat@zip.com.au \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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