LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: yuval yeret <yuval_yeret@hotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: 2.4.20-18 size-4096 memory leaks
Date: 26 Nov 2003 11:57:05 +0000	[thread overview]
Message-ID: <1069847824.2031.16.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <1069844249.3fc487195c258@imp.gcu.info>

Hi,

On Wed, 2003-11-26 at 10:57, Jean Delvare wrote:

> I just wanted to let you know that I have been experiencing similar
> leaks. So far, I wasn't enable to find where the leak was, but your
> theory matches my observations:
> 
> 1* On two systems running 2.4.20-2.4.22 kernels, I observed that the
> free memory as reported by top was going down regularly, by blocks of 4
> or 8kB at an average rate of 90kB/min. Sometimes the value would
> stabilize, but I couldn't understand why. What was lost as "free"
> memory
> increased "buffers" from the same amount.

That's not a leak, it simply sounds like cache effects.  atime updates
result in journal commits under ext3, and those use at least a couple of
buffers at a time (one for the metadata descriptor block in the journal,
one for the journal commit.)  Those aren't leaks --- they are temporary
use of cache, and once the IO has complete the memory can be immediately
reclaimed by the kernel if it is needed for anything else.

Cheers, 
 Stephen



  reply	other threads:[~2003-11-26 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 10:57 Jean Delvare
2003-11-26 11:57 ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26 14:14 yuval yeret
2003-11-26 10:24 yuval yeret
2003-11-26  9:29 yuval yeret
2003-11-26 10:11 ` Henrik Storner
2003-11-26 11:51 ` Stephen C. Tweedie

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=1069847824.2031.16.camel@sisko.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuval_yeret@hotmail.com \
    --subject='Re: 2.4.20-18 size-4096 memory leaks' \
    /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

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