From: Willy Tarreau <willy@w.ods.org>
To: Yoss <bartek@milc.com.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory leak in 2.4.33-pre1?
Date: Tue, 14 Feb 2006 01:05:30 +0100 [thread overview]
Message-ID: <20060214000529.GJ11380@w.ods.org> (raw)
In-Reply-To: <20060213214651.GA27844@milc.com.pl>
Hello,
On Mon, Feb 13, 2006 at 10:46:51PM +0100, Yoss wrote:
> Hello.
> My server have lost about ~300MB of RAM. Details:
>
> webcache:~# uname -a
> Linux webcache 2.4.33-pre1 #2 Wed Feb 8 18:26:44 CET 2006 i686 GNU/Linux
>
> No other patches. Only basic elements needed to work in network
> enviroment.
>
> webcache:~# dmesg | grep MEM
> 127MB HIGHMEM available.
> 896MB LOWMEM available.
>
> When I count memmory used by processes (column SIZE from ps or RES from
> top) there is about 650MB used. (There is only squid, named and basic
> system deamons running on that host). But:
>
> webcache:~# free -m
> total used free shared buffers cached
> Mem: 1009 996 13 0 18 32
> -/+ buffers/cache: 945 64
> Swap: 1953 0 1952
>
>
> So there is missing about ~300MB.
> If anyone wants to have more detailed info feel free to ask.
You don't have to worry. Simply check /proc/slabinfo, you'll see plenty
of memory used by dentry_cache and inode_cache and that's expected. This
memory will be reclaimed when needed (for instance by calls to malloc()).
If you don't believe me, simply allocate 1 GB in a process, then free it.
Regards,
Willy
next prev parent reply other threads:[~2006-02-14 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 21:46 Yoss
2006-02-14 0:05 ` Willy Tarreau [this message]
2006-02-14 0:34 ` Roberto Nibali
2006-02-14 4:50 ` Willy Tarreau
2006-02-14 8:22 ` Yoss
2006-02-14 8:21 ` Yoss
2006-02-14 21:43 ` Willy TARREAU
2006-02-15 9:01 ` Yoss
2006-02-15 20:11 ` Willy Tarreau
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=20060214000529.GJ11380@w.ods.org \
--to=willy@w.ods.org \
--cc=bartek@milc.com.pl \
--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
Powered by JetHome