From: Bill Hartner <bhartner@us...> - 2001-01-10 19:13:57
I did not see any response to the post I did about the inode_cache
growing after 13 hrs. when running the chat room benchmark.
How long does it take on your system before the inode_cache starts to grow ?
You may get around it by rebooting your system and then running the
I have not taken the tinme to try to figure out what is going on yet.
I have not verified if it still exists in 2.4.0.
I will be in today, call me.
IBM Linux Technology Center - kernel performance
On Wed, Jan 10, 2001 at 02:14:15PM -0500, Bill Hartner wrote:
> I did not see any response to the post I did about the inode_cache
> growing after 13 hrs. when running the chat room benchmark.
The problem is not really the inode cache, but the dcache (inode cache is just
the slave of the dcache) It's a bug in Linux dcache management. Andrea Arcangelli
fixed it for his *aa* kernels (and the 2.2 SuSE kernels), but so far he didn't
succeed in merging it to official kernels yet.
2.4.1-pre1 has dcache aging, which helps (but does not completely solve the problem).
You could try that.