public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ken Brownfield <brownfld@irridia.com>
To: Chris Chabot <chabotc@reviewboard.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
	linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Unfreeable buffer/cache problem in 2.4.17-rc1 still there
Date: Sat, 15 Dec 2001 10:09:55 -0600	[thread overview]
Message-ID: <20011215100955.B13598@asooo.flowerfire.com> (raw)
In-Reply-To: <1008419776.6780.0.camel@gandalf.chabotc.com> <20011215152446.P2431@athlon.random> <1008432321.13025.0.camel@gandalf.chabotc.com>
In-Reply-To: <1008432321.13025.0.camel@gandalf.chabotc.com>; from chabotc@reviewboard.com on Sat, Dec 15, 2001 at 05:05:20PM +0100

I think "updatedb" at 4am is what you're looking for...  How much disk
space do you have on this system?

-- 
Ken.
brownfld@irridia.com

On Sat, Dec 15, 2001 at 05:05:20PM +0100, Chris Chabot wrote:
| Ok, rc1-aa1 is installed, up and running. Since it took a little more
| then a day last time for this behavour to be displayed, i'll have to
| wait before i can report back anything usefull.
| 
| Ps, a side question. if this is 'inode' and 'dentry' cache, why isnt it
| reported as 'used by cache' in free, top, gtop, etc?
| 
| Also, why is this such a progressive problem? Even if i do a find on the
| full +/- 400 gigs, create and remove 2 gig files, create 1000 temp
| files, etc, in the first day the memory isnt 'disapearing' yet.
| (ofcource it uses a lot of mem for cache/buffers, but no 'unaccounted
| for in free or top' memory.
| 
| Will report back soon,
| 
| 	-- Chris
| 
| 
| On Sat, 2001-12-15 at 15:24, Andrea Arcangeli wrote:
| > On Sat, Dec 15, 2001 at 01:36:11PM +0100, Chris Chabot wrote:
| > > inode_cache       686896 686896    480 85862 85862    1 :  124   62
| > > dentry_cache      696810 696810    128 23227 23227    1 :  252  126
| > 
| > this is an icache/dcache problem, can you reproduce on 2.4.17rc1aa1, it
| > will shrink more aggressively.
| > 
| > really to get an even better balance we should add the icache/dcache
| > slab pages into the lru as well... that would trigger the icache/dcache
| > flushes more easily when too much ram is in those caches.
| > 
| > Andrea
| 
| 
| -
| To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at  http://vger.kernel.org/majordomo-info.html
| Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2001-12-15 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 12:36 Unfreeable buffer/cache problem in 2.4.17-rc1 still there Chris Chabot
     [not found] ` <004601c18567$a8be1600$0801a8c0@Stev.org>
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-15 16:05 Ed Tomlinson
     [not found] <Pine.LNX.4.33.0112151141280.19022-100000@coffee.psychology.mcmaster.ca>
2001-12-15 17:09 ` Chris Chabot
2001-12-16 19:39 Dmitry Volkoff
2001-12-17 17:01 ` vda
2001-12-18  4:26   ` Dmitry Volkoff
2001-12-16 20:41 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=20011215100955.B13598@asooo.flowerfire.com \
    --to=brownfld@irridia.com \
    --cc=andrea@suse.de \
    --cc=chabotc@reviewboard.com \
    --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