From: Mikel Bauer <mikel@bridgeband.net>
To: - Luis - <unix@amigo.net.gt>
Cc: linux-admin@vger.kernel.org
Subject: Re: free memory usage
Date: Fri, 09 May 2003 16:08:07 -0600 [thread overview]
Message-ID: <3EBC26C7.1010602@bridgeband.net> (raw)
In-Reply-To: <200305091458.57370.unix@amigo.net.gt>
Memory that is buffered or cached is not the same as being used. It is
memory that was used before, freed, but with the possibility of being
used again so as to speed up information retrieval. This memory is
available to whatever needs it. There probably isn't a server in
existance that doesn't cache a fair bit of memory (unless it was never
used).
- Luis - wrote:
> And what about if the mem is being cached or buffered? what can i do about it?
> can i free it?
>
> Thanks
>
> On Friday 09 May 2003 17:46, Mikel Bauer wrote:
>
>>Is memory still technically "full" (used), or is it cached? Usually the
>>kernel is smart enough to fix problems like that, and will free memory
>>that's no longer being referenced (memory leaks really only exist if an
>>app is still running, the kernel wont take away memory from a running app)
>>
>>I would take a look at your /proc/meminfo, and see if most of the "used"
>>memory is accounted for in the cache.
>
>
--
Mikel Bauer
next prev parent reply other threads:[~2003-05-09 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 11:25 free memory usage - Luis -
2003-05-09 17:29 ` Scott Taylor
2003-05-09 17:46 ` Mikel Bauer
2003-05-09 14:58 ` - Luis -
2003-05-09 21:29 ` Richard Nairn
2003-05-09 22:08 ` Mikel Bauer [this message]
2003-05-09 17:55 ` Glynn Clements
2003-05-09 12:10 ` - Luis -
-- strict thread matches above, loose matches on Subject: below --
2003-05-10 3:39 jbrown105
2003-05-10 11:15 ` Glynn Clements
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=3EBC26C7.1010602@bridgeband.net \
--to=mikel@bridgeband.net \
--cc=linux-admin@vger.kernel.org \
--cc=unix@amigo.net.gt \
/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.