From: Andreas Dilger <adilger@clusterfs.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Jakob Oestergaard <jakob@unthought.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 - large inode_cache
Date: Thu, 26 Feb 2004 10:43:38 -0700 [thread overview]
Message-ID: <20040226174338.GP1257@schnapps.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.58L.0402261109190.5003@logos.cnet>
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.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2004-02-26 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 1:33 2.4.25 - large inode_cache Jakob Oestergaard
2004-02-26 11:19 ` Christian Leber
2004-02-26 13:08 ` Marcelo Tosatti
2004-02-26 13:03 ` Jakob Oestergaard
2004-02-26 14:23 ` Marcelo Tosatti
2004-02-26 13:53 ` Jakob Oestergaard
2004-02-26 17:43 ` Andreas Dilger [this message]
2004-02-26 20:43 ` Marcelo Tosatti
2004-02-27 12:27 ` Jakob Oestergaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040226174338.GP1257@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox