From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Alan Robertson <alanr@unix.sh>, Lorn Kay <lorn_kay@hotmail.com>,
nfs@lists.sourceforge.net, linux-ha@muc.de
Subject: Re: Re: NFS as a Cluster File System.
Date: 14 Jan 2003 16:46:58 +0100 [thread overview]
Message-ID: <shsk7h720p9.fsf@charged.uio.no> (raw)
In-Reply-To: <15907.5456.68906.820989@notabene.cse.unsw.edu.au>
>>>>> " " == Neil Brown <neilb@cse.unsw.edu.au> writes:
> NFSv4 does not try to "fix" this. It makes no attempts at
> "cache coherency" beyond what NFSv2/3 provide which is "close
> to open" cohenrence, meaning that if only one process has a
> file open at a time, then everythnig will appear coherent, and
> if multiple processes have the file open at the same time, they
> need to use record locking.
Note, though, that in addition to supporting file locking, NFSv4 adds
support for file 'delegation' which allow the NFS client to do locking
entirely as a local operation (i.e. there is no need to contact the
server). For most applications, this will make locking a much faster
operation...
Cheers,
Trond
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-14 15:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 19:39 NFS as a Cluster File System Lorn Kay
2003-01-09 21:11 ` Brian Tinsley
2003-01-09 22:04 ` Brian Jackson
2003-01-09 23:02 ` Brian Tinsley
2003-01-09 21:29 ` Alan Robertson
2003-01-13 19:36 ` Neil Brown
2003-01-13 20:25 ` David B. Ritch
2003-01-13 20:40 ` Neil Brown
2003-01-13 20:50 ` David B. Ritch
2003-01-13 22:11 ` Neil Brown
2003-01-14 15:46 ` Trond Myklebust [this message]
2003-01-14 16:01 ` Kumaran Rajaram
2003-01-14 16:08 ` Trond Myklebust
2003-01-09 21:50 ` Lars Marowsky-Bree
2003-01-09 23:09 ` Brian Tinsley
2003-01-13 4:20 ` David B. Ritch
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 22:51 Lorn Kay
2003-01-10 15:01 ` Trond Myklebust
2003-01-10 17:38 ` Greg Lindahl
2003-01-12 21:23 ` Trond Myklebust
2003-01-09 23:13 Lorn Kay
2003-01-09 23:45 ` Donavan Pantke
2003-01-10 14:51 Lever, Charles
2003-01-10 15:23 ` Brian Tinsley
2003-01-10 17:19 Lorn Kay
2003-01-12 21:29 ` Trond Myklebust
2003-01-14 16:01 Lever, Charles
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=shsk7h720p9.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alanr@unix.sh \
--cc=linux-ha@muc.de \
--cc=lorn_kay@hotmail.com \
--cc=neilb@cse.unsw.edu.au \
--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.