Subject: Re: heavy file i/o on ext3 filesystem leads to huge
	ext3_inode_cache and dentry_cache that doesn't return to normal for hours
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Maarten Maathuis <madman2003@gmail.com>
Cc: Dave Kleikamp <shaggy@austin.ibm.com>, linux-kernel@vger.kernel.org
In-Reply-To: <6d4bc9fc0608040053x4d7a9e14xe9de793cd0787736@mail.gmail.com>
References: <6d4bc9fc0608030927t175f16c0kfef6a21cc521e368@mail.gmail.com>
	 <1154661560.17180.31.camel@kleikamp.austin.ibm.com>
	 <6d4bc9fc0608040053x4d7a9e14xe9de793cd0787736@mail.gmail.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Fri, 04 Aug 2006 10:43:07 +0100
Message-Id: <1154684587.23655.175.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 854
Lines: 18

Ar Gwe, 2006-08-04 am 09:53 +0200, ysgrifennodd Maarten Maathuis:
> > > Whenever there is serious hard drive activity (such as doing "slocate
> > > -u") ext3_inode_cache and dentry_cache grow to a combined 400-500 MiB.
> >
> > The behavior of slocate (updatedb) is pretty well-known, but nobody has
> > come up with a real solution.

Thats not actually true. There is patch to page back in code on a quiet
machine which is in -mm and is designed to pull stuff back after a busy
period. There was also discussion (but not yet code) for splitting the
dcache into two and being much smarter about recycling it.


-
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/