Messages in this thread | | | 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 <> | Date | Fri, 04 Aug 2006 10:43:07 +0100 |
| |
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/
| |