All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: csmithere@gmail.com
Cc: linux-nfs@vger.kernel.org
Subject: NFS faq
Date: Sat, 4 Oct 2008 16:57:35 -0400	[thread overview]
Message-ID: <20081004205735.GC2777@fieldses.org> (raw)

Do you still maintain the FAQ at nfs.sourceforge.net?

In A7:

	"There are some minor interoperability issues when applications
	running on clients make use of some of the new features of NFS
	Version 4 such as mandatory locking, share reservations, and
	delegations."

I'd remove "delegations"--they change the performance (most dramatically
if the server has to wait for a lease to time out to allow an open), but
should otherwise be transparent to applications.

The

	NFS-related kernel patches supported by Trond Myklebust
	NFS-related kernel patches supported by Neil Brown 

links should probably just be removed and replaced by a "linux
development" link to linux-nfs.org.

--b.

             reply	other threads:[~2008-10-04 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04 20:57 J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 18:18 NFS FAQ pwitting

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=20081004205735.GC2777@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=csmithere@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.