On Sat, 3 Jan 2004, Andrew Morton wrote: > John Lash <jlash _at_ speakeasy.net> wrote: > > > > As it stands, it will maintain as many unused entries as there are used entries. > > If this low memory system las a large, stable, number of inuse dentry objects, > > the unused entries will match it thereby holding double the memory and possibly > > causing the problem you see. > > Yup. There is a fix in 2.6.1-rc1 for this. Which change would that be? It would be nice to back-port that to 2.4.x if that's possible? -- http://www.munted.org.uk Your mother cooks socks in hell - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: inode_cache / dentry_cache not being reclaimed aggressivelyenough on low-memory PCsAndrew Morton
- inode_cache / dentry_cache not being reclaimed aggressively enoughon low-memory PCsAlex Buell
- Re: inode_cache / dentry_cache not being reclaimed aggressivelyenough on low-memory PCsJohn Lash
- Re: inode_cache / dentry_cache not being reclaimed aggressivelyenough on low-memory PCsAndrew Morton
- Prev by Date: Re: [minor & trivial patch] kill some potential warnings about inlinekeyword placement - 2.6.1-rc1-mm1
- Next by Date: Re: 2.6.0: atyfb broken
- Previous by thread: Re: inode_cache / dentry_cache not being reclaimed aggressivelyenough on low-memory PCs
- Next by thread: Re: inode_cache / dentry_cache not being reclaimed aggressivelyenough on low-memory PCs
- Indexes:[Main][Thread]