LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: yuval yeret <yuval_yeret@hotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-18 size-4096 memory leaks
Date: Wed, 26 Nov 2003 11:57:29 +0100	[thread overview]
Message-ID: <1069844249.3fc487195c258@imp.gcu.info> (raw)

Hi Yuval, hi list,

> I'm seeing a constant leak in size-4096 on a machine running
> 2.4.20-18 SMP BIGMEM, which might / might not be related to the
> machine finally going out of memory and going into a hang.

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. Still that value doesn't
exceed a few dozen MB and sometimes goes does by large blocks, so I was
wondering if there was a real leak or if it was just some kind of
regular prebuffering.

2* On two other, seemingly similar systems, the memory leak wouldn't
occur. It happens that these two systems do *not* use ext3, while the
fisrt two *do* use ext3.

3* The leak isn't distribution specific. I experienced it on both a
Mandrake-shipped kernel and a self-compiled one on a Slackware system.

Your theory that it comes from the ext3 driver makes full sense. I'll
confirm that later today, by using ext2 only on one of the leaking
systems (without changing kernels of course).

The other leaking system is used as a development server. It used to
become very slow after several days. We are now restarting it every
monday and have no significant slowdown anymore. Having other things to
do, I stopped my experiments there, but could do some more now if it
can help.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 10:57 Jean Delvare [this message]
2003-11-26 11:57 ` Stephen C. Tweedie
  -- 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=1069844249.3fc487195c258@imp.gcu.info \
    --to=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).