From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Question: When NFS client check dir's permission,
	it	does not check the cache data
Date: Tue, 26 Jun 2007 23:09:14 -0400
Message-ID: <1182913754.12836.61.camel@heimdal.trondhjem.org>
References: <467F8247.9060607@cn.fujitsu.com>
	<1182802099.6163.33.camel@heimdal.trondhjem.org>
	<4681BC44.6000605@cn.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Wei Yongjun <yjwei@cn.fujitsu.com>
In-Reply-To: <4681BC44.6000605@cn.fujitsu.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Wed, 2007-06-27 at 09:24 +0800, Wei Yongjun wrote:

> I think code "status = nfs_access_get_cached(inode, cred, &cache);" can do
> this. And it works.
> Other question: why only optimize all write operations, read operations
> are not optimized? If read options is optimized, it can do the same things,
> do not use access to check permissions, and server will check permissions
> when we perform the read op.

Huh? What read operations are we failing to optimise and how?

Trond


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs