All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jamie Lokier <jamie@shareable.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...)
Date: Fri, 10 Oct 2003 11:32:24 -0400	[thread overview]
Message-ID: <16262.53512.249701.158271@charged.uio.no> (raw)
In-Reply-To: <20031010143553.GA28795@mail.shareable.org>

>>>>> " " == Jamie Lokier <jamie@shareable.org> writes:

     > Trond Myklebust wrote:
    >> Sure. We might even try actually implementing leases on NFSv4
    >> for delegated files.

     > That would be nice.  (Aside: Can NFSv4 do anything like
     > dnotify, or am I restricted to, in effect, keeping many files
     > open to detect changes in any of them?)

Delegations for directories are in the pipeline for the next minor
revision of the protocol (NFSv4.1). Delegations are such a new feature
to NFS that it was decided to restrict them to files only to give us
time to learn how best to use them.

I can't tell as of yet whether or not the model chosen will include
all the features of dnotify (for instance recall in case the
attributes change on a subfile is a subject of hot debate), but
certainly some of us are pushing for something like this.

     > Generally NFSv4 sounds like the way to go.  Should I be
     > recommending it to all my friends yet, is the implementation
     > ready for that?

The client implementation in 2.6.0 is still lacking several important
features, including locking, ACLs, delegation support and recovery of
state (in case of server reboot or network partitions). I'm hoping
Andrew/Linus will allow me to send updates once the early 2.6.x
codefreeze period is over.

That said, I definitely encourage people to test out the existing code
for stability, and I will be offering an 'NFS_ALL' series with those
features that are missing from the main tree as and when I judge they
are approaching release quality.

Cheers,
  Trond

  reply	other threads:[~2003-10-10 15:32 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-09 22:16 statfs() / statvfs() syscall ballsup Trond Myklebust
2003-10-09 22:26 ` Linus Torvalds
2003-10-09 23:19   ` Ulrich Drepper
2003-10-10  0:22     ` viro
2003-10-10  4:49       ` Jamie Lokier
2003-10-10  5:26         ` Trond Myklebust
2003-10-10 12:37           ` Jamie Lokier
2003-10-10 13:46             ` Trond Myklebust
2003-10-10 14:35               ` Jamie Lokier
2003-10-10 15:32                 ` Trond Myklebust [this message]
2003-10-10 15:53                   ` Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...) Jamie Lokier
2003-10-10 16:07                     ` Trond Myklebust
2003-10-10 15:55                   ` Michael Shuey
2003-10-10 16:20                     ` Trond Myklebust
2003-10-10 16:45                     ` J. Bruce Fields
2003-10-10 14:39               ` statfs() / statvfs() syscall ballsup Jamie Lokier
2003-10-09 23:31   ` Trond Myklebust
2003-10-10 12:27   ` Joel Becker
2003-10-10 14:59     ` Linus Torvalds
2003-10-10 15:27       ` Joel Becker
2003-10-10 16:00         ` Linus Torvalds
2003-10-10 16:26           ` Joel Becker
2003-10-10 16:50             ` Linus Torvalds
2003-10-10 17:33               ` Joel Becker
2003-10-10 17:51                 ` Linus Torvalds
2003-10-10 18:13                   ` Joel Becker
2003-10-10 16:27           ` Valdis.Kletnieks
2003-10-10 16:33           ` Chris Friesen
2003-10-10 17:04             ` Linus Torvalds
2003-10-10 17:07               ` Linus Torvalds
2003-10-10 17:21                 ` Joel Becker
2003-10-10 16:01         ` Jamie Lokier
2003-10-10 16:33           ` Joel Becker
2003-10-10 16:58             ` Chris Friesen
2003-10-10 17:05               ` Trond Myklebust
2003-10-10 17:20               ` Joel Becker
2003-10-10 17:33                 ` Chris Friesen
2003-10-10 17:40                 ` Linus Torvalds
2003-10-10 17:54                   ` Trond Myklebust
2003-10-10 18:05                     ` Linus Torvalds
2003-10-10 20:40                       ` Trond Myklebust
2003-10-10 21:09                         ` Linus Torvalds
2003-10-10 22:17                           ` Trond Myklebust
2003-10-11  2:53                     ` Andrew Morton
2003-10-11  3:47                       ` Trond Myklebust
2003-10-10 18:05                   ` Joel Becker
2003-10-10 18:31                     ` Andrea Arcangeli
2003-10-10 20:33                     ` Helge Hafting
2003-10-10 20:07             ` Jamie Lokier
2003-10-12 15:31             ` Greg Stark
2003-10-12 16:13               ` Linus Torvalds
2003-10-12 22:09                 ` Greg Stark
2003-10-13  8:45                   ` Helge Hafting
2003-10-15 13:25                     ` Ingo Oeser
2003-10-15 15:03                       ` Greg Stark
2003-10-15 18:37                         ` Helge Hafting
2003-10-16 10:29                         ` Ingo Oeser
2003-10-16 14:02                           ` Greg Stark
2003-10-21 11:47                             ` Ingo Oeser
2003-10-10 18:20           ` Andrea Arcangeli
2003-10-10 18:36             ` Linus Torvalds
2003-10-10 19:03               ` Andrea Arcangeli
2003-10-09 23:16 ` Andreas Dilger
2003-10-09 23:24   ` Linus Torvalds

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=16262.53512.249701.158271@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Misc NFSv4 (was Re: statfs() / statvfs() syscall ballsup...)' \
    /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

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.