From: Casey Bodley <cbodley@umich.edu>
To: linux-nfs@vger.kernel.org
Cc: Olga Kornievskaia <aglo@citi.umich.edu>
Subject: dentry cache memory usage
Date: Mon, 26 Jul 2010 11:21:40 -0400 [thread overview]
Message-ID: <AANLkTinSHDKPO5frmr4sik6ZnIZyOpfsDvXc20W74Df1@mail.gmail.com> (raw)
I'm a developer at CITI working on the windows pnfs client. We've
been looking into some optimizations for our name and attribute
caches, mainly involving the use of pools to avoid allocating memory
for each new entry.
We're looking for a sensible initial/maximum pool size. Once the
maximum pool size is reached, we'll start scavenging the least
recently used entries. Does the linux client impose any limits on the
size of the dentry cache?
I'm also curious what time limits you're using before expiring cached
attributes and lookups.
I suppose I'm just asking for magic numbers here, in the hope that
smart people have tested and benchmarked this stuff in the linux
client.
Thanks,
Casey
next reply other threads:[~2010-07-26 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 15:21 Casey Bodley [this message]
2010-07-26 15:33 ` dentry cache memory usage Trond Myklebust
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=AANLkTinSHDKPO5frmr4sik6ZnIZyOpfsDvXc20W74Df1@mail.gmail.com \
--to=cbodley@umich.edu \
--cc=aglo@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).