Messages in this thread | | | Date | Thu, 26 Feb 2004 17:43:49 -0300 (BRT) | From | Marcelo Tosatti <> | Subject | Re: 2.4.25 - large inode_cache |
| |
On Thu, 26 Feb 2004, Andreas Dilger wrote:
> On Feb 26, 2004 11:23 -0300, Marcelo Tosatti wrote: > > On Thu, 26 Feb 2004, Jakob Oestergaard wrote: > > > On Thu, Feb 26, 2004 at 10:08:23AM -0300, Marcelo Tosatti wrote: > > > > This should be normal behaviour -- the i/d caches grew because of file > > > > system activitity. This memory will be reclaimed in case theres pressure. > > > > > > But how is "pressure" defined? > > > > > > Will a heap of busy knfsd processes doing reads or writes exert > > > pressure? Or is it only local userspace that can pressurize the VM (by > > > either anonymously backed memory or file I/O). > > > > Any allocator will cause VM pressure. > > But won't all of the knfsd allocations be by necessity GFP_NOFS to avoid > deadlocks, so they will be unable to clear inodes or dentries? Both > shrink_icache_memory() and shrink_dcache_memory() do nothing if __GFP_FS > isn't set so if there is no user-space allocation pressure we will never > get into the dcache/icache freeing paths from knfsd allocations.
Hi Andreas,
AFAICS knfsd does not allocate using GFP_NOFS.
- 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/
| |