From: Jakob Oestergaard <jakob@unthought.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Andreas Dilger <adilger@clusterfs.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 - large inode_cache
Date: Fri, 27 Feb 2004 13:27:14 +0100 [thread overview]
Message-ID: <20040227122714.GT29776@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.58L.0402261742090.8840@logos.cnet>
On Thu, Feb 26, 2004 at 05:43:49PM -0300, Marcelo Tosatti wrote:
>
...
> > > 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.
So far, it looks like the vm_vfs_scan_ratio setting of '3' (instead of
'6' which was the default) made a big difference.
Currently the machine is using about ~600MB for cache (up from ~100MB),
and about 150MB for buffers (up from 80-100MB).
I'm going to let it run a little longer just with this setting, before
experimenting further.
I'll ask around about the perceived performance of the machine, and pay
attention to it myself. I'll post the results monday or tuesday (not a
lot of interactive users during the weekend ;)
Again, thanks a lot for the quick feedback!
/ jakob
prev parent reply other threads:[~2004-02-27 12:28 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
2004-02-26 20:43 ` Marcelo Tosatti
2004-02-27 12:27 ` Jakob Oestergaard [this message]
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=20040227122714.GT29776@unthought.net \
--to=jakob@unthought.net \
--cc=adilger@clusterfs.com \
--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