From: David Chow <davidchow@shaolinmicro.com>
To: trond.myklebust@fys.uio.no, linux-fsdevel@vger.kernel.org
Subject: Problems of lookup_revalidate
Date: Mon, 26 Aug 2002 23:53:22 +0800 [thread overview]
Message-ID: <3D6A4EF2.1070607@shaolinmicro.com> (raw)
Trond,
I think the strategy used in 2.4.19 for NFS dentry and inode updates are
too weak. May be you have being pushing too hard on optimizing
performance (fewer lookups and revalidate). But I have problems that the
client d_cache() inconsistency. It seems when the server changes file
mode or ownership, the client is not updated properly unless I explicity
add a file in the parent directory at the server which triggers the
mtime of the parent, the client hardly update the dcache and inode
parameters properly. Please clarify if my guess is wrong. Thanks.
David
next reply other threads:[~2002-08-26 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 15:53 David Chow [this message]
2002-08-26 16:10 ` Problems of lookup_revalidate Trond Myklebust
2002-08-27 1:35 ` David Chow
2002-08-27 18:00 ` Trond Myklebust
2002-08-29 9:26 ` David Chow
2002-08-29 9:31 ` Trond Myklebust
2002-08-29 9:34 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 15:26 Bryan Henderson
2002-08-29 23:19 ` Trond Myklebust
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=3D6A4EF2.1070607@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-fsdevel@vger.kernel.org \
--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 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.