From: Chris Chabot <chabotc@reviewboard.com>
To: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Severe Linux 2.4 kernel memory leakage
Date: 25 Nov 2001 16:30:26 +0100 [thread overview]
Message-ID: <1006702226.1316.2.camel@gandalf.chabotc.com> (raw)
In-Reply-To: <tgy9kuevtw.fsf@mercury.rus.uni-stuttgart.de>
In-Reply-To: <1006699767.1178.0.camel@gandalf.chabotc.com> <tgy9kuevtw.fsf@mercury.rus.uni-stuttgart.de>
The kernel i ran for about a month was kernel 2.4.11.
Ofcource i am aware that the memory usage grows as more memory is used
for buffers/cache. (specialy since its also a large file server).
However if you check my 'free' output, and the ps aux output you will
notice that the 430Mb used is with the cache and buffer usage already
subtracted from the 'total usage' (else usage is just below 1 gig).
Of 430Mb, (counting ps aux res values), just below 80 Mb is used by the
applications. the rest is just 'missing'.
So the current memory division is about (sources: application = added ps
aux output, buffer/cache/free = 'free' command, sysv shm from 'ipcs')
Applications: 80Mb
Buffers: 127Mb
Cache: 460Mb
Sysv shm: 0
Free: 9.5Mb
memory total 1Gb
Unaccounted +/- 360Mb
ps, yes i did check /dev/shm, and 'ipcs' and no memory is used as sysv
shared memory
-- Chris
On Sun, 2001-11-25 at 16:03, Florian Weimer wrote:
> Chris Chabot <chabotc@reviewboard.com> writes:
>
> > When the box keeps on running for about a month,
>
> Which kernels have you run for about a month, and which ones showed
> this extreme behavior? Obviously not 2.4.15...
>
> The amount of available memory decreasing is quite normal, due to the
> growing cache.
>
> --
> Florian Weimer Florian.Weimer@RUS.Uni-Stuttgart.DE
> University of Stuttgart http://cert.uni-stuttgart.de/
> RUS-CERT +49-711-685-5973/fax +49-711-685-5898
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-11-25 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 14:49 Chris Chabot
2001-11-25 15:03 ` Florian Weimer
2001-11-25 15:41 ` Phil Sorber
2001-11-25 15:53 ` François Cami
2001-11-25 17:17 ` Phil Sorber
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
2001-11-26 20:15 ` Bill Davidsen
2001-11-25 15:30 ` Chris Chabot [this message]
2001-11-25 15:51 ` Chris Chabot
2001-11-25 18:44 ` Chris Chabot
2001-11-25 15:55 ` Mr. Shannon Aldinger
2001-11-25 16:14 ` Florian Weimer
2001-11-26 15:11 ` Christoph Rohland
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=1006702226.1316.2.camel@gandalf.chabotc.com \
--to=chabotc@reviewboard.com \
--cc=Florian.Weimer@RUS.Uni-Stuttgart.DE \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®