From: Mark Goodman <mgoodman@CSUA.Berkeley.EDU>
To: nfs@lists.sourceforge.net
Subject: http://client.linux-nfs.org/Linux-2.6.x/2.6.10/linux-2.6.10-33-access_cache.dif
Date: Sat, 05 Feb 2005 01:50:47 -0800 [thread overview]
Message-ID: <420496F7.9080900@csua.berkeley.edu> (raw)
This patch appears to have the effect that non-existent files don't get
cached. When I apply it to 2.6.10, a C preprocessor workload that
involves opening lots of non-existent files slows down by an order of
magnitude and I notice tens of thousands of NFS ACCESS calls per second
according to nfsstat.
Mark
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-02-05 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 9:50 Mark Goodman [this message]
2005-02-06 0:24 ` [NFS] http://client.linux-nfs.org/Linux-2.6.x/2.6.10/linux-2.6.10-33-access_cache.dif Trond Myklebust
2005-02-06 1:42 ` Mark Goodman
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=420496F7.9080900@csua.berkeley.edu \
--to=mgoodman@csua.berkeley.edu \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.