From: Mike Eisler <mike@eisler.com>
To: nfs@lists.sourceforge.net
Subject: RE: disable caching in NFS
Date: Fri, 06 Jun 2003 13:54:06 -0700 [thread overview]
Message-ID: <3EE0FF6E.8010609@eisler.com> (raw)
The application (vi) is opening the file, and
the Linux NFS client should be implementing
close-to-open semantics (meaning that the client will
revalidate its cache against the server upon every open).
Thus, this should not be necessary. Of course, if the server does not
update the file's modification time upon every write, or
if it does, but uses coarse granularity (e.g. one second),
then close-to-open semantics won't work. In that
event, the strategies Chuck Lever mentioned are among
what you can use to force the cache to be flushed or
unused.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-06-06 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 20:54 Mike Eisler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-04 21:10 disable caching in NFS Lever, Charles
2003-06-04 19:05 David Myer
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=3EE0FF6E.8010609@eisler.com \
--to=mike@eisler.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