All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: CaT <cat@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc7: memory leak?
Date: Thu, 17 Jan 2008 13:07:12 +0100	[thread overview]
Message-ID: <1200571632.28661.13.camel@twins> (raw)
In-Reply-To: <20080117114050.GR3940@zip.com.au>


On Thu, 2008-01-17 at 22:40 +1100, CaT wrote:
> On Thu, Jan 17, 2008 at 12:22:03PM +0100, Peter Zijlstra wrote:
> > On Thu, 2008-01-17 at 17:34 +1100, CaT wrote:
> > > cache). During the rsync the memory used grew to just shy of 1.6gig and
> > > now, about 2 hours after the rsync has well and truly finished, the used
> > > memory is at 1.23gig. This is what free reports:
> > > 
> > >              total       used       free     shared    buffers cached
> > > Mem:       2058128    1994468      63660          0     688604 11432
> > > -/+ buffers/cache:    1294432     763696
> > > Swap:      1048568          0    1048568
> > 
> > How much memory does:
> > 
> >   echo 3 > /proc/sys/vm/drop_caches
> > 
> > gain you?
> 
> 56M used now. 

Good :-)

> 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.

> I assume that this would not cause an oom situation and would be
> freed up if all that memory really did need to be used.

Correct.



  reply	other threads:[~2008-01-17 12:07 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 [this message]
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

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=1200571632.28661.13.camel@twins \
    --to=peterz@infradead.org \
    --cc=cat@zip.com.au \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.