From: Steve Dickson <SteveD@RedHat.com>
To: Andreas Gruenbacher <agruen@suse.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Access cache forgetting mode bits
Date: Sun, 31 Aug 2003 16:33:44 -0400 [thread overview]
Message-ID: <3F525BA8.9020904@RedHat.com> (raw)
In-Reply-To: <1062107512.2121.25.camel@bree.suse.de>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Hello,
I'm thinking there might even be a better way to cache these bits...
It seems the OS calls nfs_permission() to test each permission bit which
in turn
causes an otw access rpc for every call (assuming the same person and same
bit is *not* asked for ) and even with Andreas patch's there are at
least two
rpcs for one access call....
Now what if on the first access call, we get *all* of the access bits
from the
server and cache them locally (i.e. in cache->mask). That way when
nfs_permission()
is called again, all if the needed info is there... The attached patch
does just that
and it really seems to cut down on the amount access rpc needed...
Thoughts?
SteveD.
[-- Attachment #2: linux-2.4.21-nfs-accesscache.patch --]
[-- Type: text/plain, Size: 364 bytes --]
--- linux-2.4.21/fs/nfs/dir.c.diff 2003-08-28 12:13:22.000000000 -0400
+++ linux-2.4.21/fs/nfs/dir.c 2003-08-28 12:13:47.000000000 -0400
@@ -1278,7 +1278,7 @@ nfs_permission(struct inode *inode, int
if (cache->cred)
put_rpccred(cache->cred);
cache->cred = cred;
- cache->mask = mask;
+ cache->mask |= mask;
cache->err = error;
return error;
}
next prev parent reply other threads:[~2003-08-31 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 16:39 [PATCH] Access cache forgetting mode bits Steve Dickson
2003-08-28 21:51 ` Andreas Gruenbacher
2003-08-29 13:14 ` Steve Dickson
2003-08-31 20:33 ` Steve Dickson [this message]
2003-08-31 23:25 ` Andreas Gruenbacher
2003-09-01 3:22 ` Steve Dickson
2003-09-01 3:52 ` Trond Myklebust
2003-09-01 13:13 ` Steve Dickson
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=3F525BA8.9020904@RedHat.com \
--to=steved@redhat.com \
--cc=agruen@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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