From: Steve Dickson <SteveD@redhat.com>
To: nfs@lists.sourceforge.net
Subject: [PATCH] Access cache forgetting mode bits
Date: Thu, 28 Aug 2003 12:39:11 -0400 [thread overview]
Message-ID: <3F4E302F.5060409@RedHat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
While debugging something else, I notice that every time
I did a ls on a nfs mounted directory a wto ACCESS rpc was
*always* happening (with a 2.4.21 kernel). Taking a closer
look it turns out the access cache was dropping previous
access bits. Here is the scenario...
nfs_permission is called with mode = MAY_EXEC
the cached value is Zero so an ACCESS rpc is done.
after the rpc, the cached value is _set_ to MAY_EXEC
then nfs_permission is called with mode = MAY_READ
the cached value is MAY_EXEC, so an ACCESS rpc is done.
after the rpc, the cache value is _set_ to MAY_READ
again, nfs_permission is called with mode = MAY_EXEC
this time the cached value is MAY_READ so _again_ an RPC is done
after the rpc, the cached value is _set_ to MAY_EXEC
Its a vicious cycle...
So this patch changes the setting of the masked value
to the or-ing of the masked value. This cause the
previous bits to be remembered thus cutting down on
the number of otw rpcs...
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 reply other threads:[~2003-08-28 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 16:39 Steve Dickson [this message]
2003-08-28 21:51 ` [PATCH] Access cache forgetting mode bits Andreas Gruenbacher
2003-08-29 13:14 ` Steve Dickson
2003-08-31 20:33 ` Steve Dickson
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=3F4E302F.5060409@RedHat.com \
--to=steved@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox