From: David Schwartz <davids@webmaster.com>
To: <kpierre@fit.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Memory Leaking. Help!
Date: Mon, 15 Apr 2002 17:36:01 -0700 [thread overview]
Message-ID: <20020416003603.AAA11784@shell.webmaster.com@whenever> (raw)
In-Reply-To: <3CBAF8EC.6070403@fit.edu>
On Mon, 15 Apr 2002 11:59:40 -0400, Kervin Pierre wrote:
>Eugenio Mastroviti wrote:
>>much data as it can in memory. The actual memory in use (check with
>>'free') is total-(buffers+cache)= 2.2-(0.37+1.51)GB=about 320 MB, which
>
>This is interesting. What exactly is buffers and cache used for?
It is used to keep information that the kernel might otherwise throw away in
case it is needed later. It is also used to accumulate writes so that they
can be made at a time where they can be done more efficiently.
>I had the same issue with the original poster with a new server. A
>fresh install with nothing significant running ( no bind nor sendmail,
>etc. ) reported that over 450 out of 512 MB was used, but looking at the
>process usage on top I barely got 5% memory usage by process. If the
>above calculation ( memory use = total - buffers - cache ) is correct
>then the memory use drops to ~100 MB.
So you now have a ton of information. You have 512Mb of physical RAM, 450 of
that is being used. 100Mb of that is process memory, 350Mb of that is buffers
and cache.
>I guess what's confusing is that total memory usuage is including
>buffers and cache. If that memory is available to applications,
>shouldn't it be removed from the "total used" figure?
Are you arguing that you shouldn't have all the information the kernel is
providing you? That some of it should be hidden from you and memory should be
said to be free when it really isn't?
All of your physical memory, less what is used by the kernel itself, is
always available to applications. That memory is being used. Really.
If you don't want your memory to be used, take it out of your computer. You
paid good money for it. The kernel is using it. You should be happy.
DS
next prev parent reply other threads:[~2002-04-16 0:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 12:23 Memory Leaking. Help! ivan
2002-04-14 13:15 ` Itai Nahshon
2002-04-14 14:05 ` Alan Cox
2002-04-14 22:51 ` ivan
2002-04-15 0:10 ` Alan Cox
2002-04-15 0:28 ` ivan
2002-04-15 5:18 ` xystrus
2002-04-15 6:10 ` john slee
2002-04-15 9:09 ` Alan Cox
2002-04-15 10:00 ` David Schwartz
2002-04-15 12:25 ` Eugenio Mastroviti
2002-04-15 15:59 ` Kervin Pierre
2002-04-16 0:36 ` David Schwartz [this message]
2002-04-15 11:30 ` Roy Sigurd Karlsbakk
2002-04-15 0:03 ` Tomasz Rola
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=20020416003603.AAA11784@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=kpierre@fit.edu \
--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