From: Chris Chabot <chabotc@reviewboard.com>
To: linux-kernel@vger.kernel.org
Cc: hahn@physics.mcmaster.ca, andrea@suse.de,
marcelo@conectiva.com.br, brownfld@irridia.com
Subject: Re: Unfreeable buffer/cache problem in 2.4.17-rc1 still there
Date: 15 Dec 2001 18:09:00 +0100 [thread overview]
Message-ID: <1008436141.13195.0.camel@gandalf.chabotc.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112151141280.19022-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.33.0112151141280.19022-100000@coffee.psychology.mcmaster.ca>
Mark Han wrote,
> first, forget silly crap like top; look at the /proc files.
> inode/dentry caches are just slab caches, which afaik
> are not considered part of the 'cached' that top is talking about.
> (since top preceeds slab and is referring to buffer+page caches.)
Man somebody got out of the wrong side of the bed this morning ;-) The
problem is that those prety user end lights are the only things the user
see's ;-) So it might be worth considering exporting this 'secret'
information to the user end (count it as cache in /proc/memusage?)
> what makes you think there's anything wrong with this? you have tons of
> memory, and aren't using it hard, so the kernel uses it to cache files,
> inodes, dentries, etc.
I know, cache is good. However first of all, 400 to 600 mb of cache used
for dentries/inodes seems a little steep to me (as not kernel hacker),
and when i do fire up memory hogging applications (mysql,apache,java
etc) the 'evaporated' memory is not returned for those applications.
Resulting in heavy swapping and a non-responsive system. For a dual p3
with 1 gig of ram, this feels like a problem, yes ;-)
do note then when i do a simple find /, it do see the memory being used
in cached and buffers. This is not the case for the 'missing memory'
Ken Brownfield wrote,
> I think "updatedb" at 4am is what you're looking for... How much disk
> space do you have on this system?
The system has 2 x 18Gb scsi disks (/ and /home) and a single raid0 volume (4x 80 gig ide) as archival storage. Doing a find | wc -l on the archives alone tells me i have more then 340000 files there.. (ranging between a few bytes to > 1 gig)
But indeed, when i run updatedb, the problem of non-visable memory (for
me using top / free anyways) does apear.. good catch!
Andrea wrote,
> this is an icache/dcache problem, can you reproduce on 2.4.17rc1aa1,
> it will shrink more aggressively.
doing that (updatedb), i dont have to wait a day or so to see what
happens, mem free (+buffers + cache from /proc/meminfo) is around 550Mb,
'used memory' (counting ps aux res usage) is < 100Mb. So quite a couple
of megabytes have disapeard again ;/
-- Chris
next parent reply other threads:[~2001-12-15 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0112151141280.19022-100000@coffee.psychology.mcmaster.ca>
2001-12-15 17:09 ` Chris Chabot [this message]
2001-12-16 20:41 Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2001-12-16 19:39 Dmitry Volkoff
2001-12-17 17:01 ` vda
2001-12-18 4:26 ` Dmitry Volkoff
2001-12-15 16:05 Ed Tomlinson
[not found] <004601c18567$a8be1600$0801a8c0@Stev.org>
2001-12-15 12:36 ` Chris Chabot
2001-12-15 13:42 ` Chris Chabot
2001-12-15 14:24 ` Andrea Arcangeli
2001-12-15 16:05 ` Chris Chabot
2001-12-15 16:09 ` Ken Brownfield
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=1008436141.13195.0.camel@gandalf.chabotc.com \
--to=chabotc@reviewboard.com \
--cc=andrea@suse.de \
--cc=brownfld@irridia.com \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®