From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: 2.6.5-rc3-mm4 tmpfs, free and free memory reporting
Date: Sun, 25 Apr 2004 23:03:38 +1000 [thread overview]
Message-ID: <20040425130338.GB2011@zip.com.au> (raw)
I noticed that the OoM killer was being rather brutal to my tasks
even though free was reporting that I had 150meg of ram left. It wasn't
until much later that I realise that I have tmpfs being used as /tmp
and I checked that. Once I cleaned that up a big all was well. The
hassle was, the memory used by tmpfs was being reported as being used
by the cache. That may be so internally but shouldn't it be reported
as actually used ram as it cannot be dumped for processes like a normal
disk cache can and therefore cannot be considered to be 'free' ram.
--
Red herrings strewn hither and yon.
next reply other threads:[~2004-04-25 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 13:03 CaT [this message]
2004-04-25 16:50 ` 2.6.5-rc3-mm4 tmpfs, free and free memory reporting Hugh Dickins
2004-04-26 2:30 ` CaT
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=20040425130338.GB2011@zip.com.au \
--to=cat@zip.com.au \
--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