From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jesse Colmenares <jcolmenares@cantv.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS servers and ACCESS procedure
Date: 06 Aug 2003 08:05:59 +0200 [thread overview]
Message-ID: <shsbrv31fso.fsf@charged.uio.no> (raw)
In-Reply-To: <3F301DF5.4000002@cantv.net>
> The question is: There are a way no disable the ACCESS
> cheching on NFS version 3 clients o servers?
Not really. However there is a patch to make linux cache those ACCESS
checks in order to reduce the number of RPC calls. It has a very
noticable effect if you are running as root (for which the current
algorithm is very inefficient).
IOW: you have 3 obvious solutions.
1) Use NFSv2...
2) You could backport the ACCESS caching patch
http://www.fys.uio.no/~trondmy/src/2.4.19/linux-2.4.19-21-access.dif
to RedHat's 2.4.18 kernel.
3) Upgrade to the RedHat 2.4.20 errata kernel, and apply the ACCESS
caching patch for 2.4.20 to that.
Alternatively, RedHat may already have applied the ACCESS patch in
their rawhide kernels? Perhaps Steve Dickson could comment on that?
Cheers,
Trond
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-08-06 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 21:13 NFS servers and ACCESS procedure Jesse Colmenares
2003-08-06 6:05 ` Trond Myklebust [this message]
2003-08-06 12:07 ` 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=shsbrv31fso.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=jcolmenares@cantv.net \
--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.