From: Chris Friesen <cfriesen@nortelnetworks.com>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org, root@chaos.analogic.com,
"Kasper Sandberg" <lkml@metanurb.dk>,
"Kristian Sørensen" <ks@cs.aau.dk>,
umbrella@cs.aau.dk
Subject: Re: Gigantic memory leak in linux-2.6.[789]!
Date: Fri, 22 Oct 2004 10:32:40 -0600 [thread overview]
Message-ID: <41793628.30208@nortelnetworks.com> (raw)
In-Reply-To: <200410221215.32597.gene.heskett@verizon.net>
Gene Heskett wrote:
> Stable, yes. But only after about 3 or 4 iterations. The first 3
> rather handily used 500+ megs of memory that I did not get back when
> I stopped it and cleaned up the mess.
Did you run a memory hog to put memory pressure on the system?
The following is with 2.6.9-rc4
-bash-2.05b$ while true ; do tar -xjf linux-2.6.7.tar.bz2 ; rm -rf linux-2.6.7 ;
vmstat ; done
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy wa id
1 0 0 1675768 104004 112576 0 0 0 1 11 2 0 0 0 10
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy wa id
1 1 0 1649032 110792 112724 0 0 0 1 11 3 0 0 0 10
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy wa id
1 0 0 1630472 118580 112620 0 0 0 2 11 3 0 0 0 10
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy wa id
1 0 0 1607560 125500 112636 0 0 0 2 11 3 0 0 0 10
After running a memory hog,
-bash-2.05b$ vmstat
procs memory swap io system cpu
r b swpd free buff cache si so bi bo in cs us sy wa id
0 0 0 1890248 672 4836 0 0 0 3 11 3 0 0 0 10
Looks like the cached memory all got freed, which is exactly as expected.
Chris
next prev parent reply other threads:[~2004-10-22 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 14:13 Gigantic memory leak in linux-2.6.[789]! Kristian Sørensen
2004-10-22 14:32 ` Kasper Sandberg
2004-10-22 15:07 ` Richard B. Johnson
2004-10-22 15:50 ` Kristian Sørensen
2004-10-22 16:12 ` Richard B. Johnson
2004-10-22 19:24 ` Kristian Sørensen
2004-10-22 19:20 ` Richard B. Johnson
2004-10-22 19:33 ` Chris Friesen
2004-10-22 16:15 ` Gene Heskett
2004-10-22 16:28 ` Andre Tomt
2004-10-22 16:32 ` Chris Friesen [this message]
2004-10-23 0:51 ` David Lang
2004-10-24 14:14 ` Bill Davidsen
2004-10-24 16:04 ` Tommy Reynolds
2004-10-25 22:11 ` Bill Davidsen
2004-10-25 22:47 ` David Lang
2004-10-23 1:44 ` Bernd Eckenfels
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=41793628.30208@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=gene.heskett@verizon.net \
--cc=ks@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=root@chaos.analogic.com \
--cc=umbrella@cs.aau.dk \
/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;
as well as URLs for NNTP newsgroup(s).