From: Andi Kleen <ak@muc.de>
To: ptb@it.uc3m.es
Cc: linux-kernel@vger.kernel.org
Subject: Re: Severe Linux 2.4 kernel memory leakage
Date: 25 Nov 2001 18:03:10 +0100 [thread overview]
Message-ID: <m3lmgug4vl.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1006699767.1178.0.camel@gandalf.chabotc.com> <200111251527.QAA05393@nbd.it.uc3m.es>
In-Reply-To: "Peter T. Breuer"'s message of "Sun, 25 Nov 2001 16:30:13 +0100"
"Peter T. Breuer" <ptb@it.uc3m.es> writes:
> "A month of sundays ago Chris Chabot wrote:"
> > The box has ran Redhat 7.1 and 7.2, with plain vanilla linux kernels
> > 2.4.9 upto 2.4.15, in all situations the same problem appeared.
> >
> > The problem is that when the box boots up, it uses about 60Mb of memory.
> > However after only 1 1/2 days, the memory usage is already around 430Mb
> > (!!). (this is ofcource used - buffers - cache, as displayed by 'free').
>
> I also have this problem. Unknown circumstances provoke it. Kernel
> 2.4.9 to 2.4.13. When it occurs I lose about 30MB a day.
Compare snapshots of /proc/slabinfo before and after.
It may be completely harmless; e.g. a slab cache. free is unfortunately
quite misleading with newer kernels; it doesn't give information about
many important caches (e.g. not about the slab caches)
-Andi
next prev parent reply other threads:[~2001-11-25 17:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 14:49 Severe Linux 2.4 kernel memory leakage Chris Chabot
2001-11-25 15:03 ` Florian Weimer
2001-11-25 15:30 ` Chris Chabot
2001-11-25 15:41 ` Phil Sorber
2001-11-25 15:51 ` Chris Chabot
2001-11-25 17:17 ` Phil Sorber
2001-11-25 18:44 ` Chris Chabot
2001-11-25 15:53 ` François Cami
2001-11-25 15:55 ` Mr. Shannon Aldinger
2001-11-25 16:14 ` Florian Weimer
2001-11-26 15:11 ` Christoph Rohland
2001-11-25 15:10 ` James Morris
2001-11-25 15:19 ` Chris Chabot
2001-11-25 15:27 ` Peter T. Breuer
2001-11-25 15:39 ` Chris Chabot
2001-11-25 17:03 ` Andi Kleen [this message]
2001-11-26 20:15 ` Bill Davidsen
2001-11-26 6:49 ` Mike Galbraith
2001-11-26 9:50 ` Chris Chabot
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=m3lmgug4vl.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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.