From: "J. Bruce Fields" <bfields@fieldses.org>
To: Eric Veith <ERVEITH@de.ibm.com>
Cc: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
linux-nfs-owner@vger.kernel.org
Subject: Re: nfs4 write delegation status
Date: Thu, 23 Jul 2009 09:00:39 -0400 [thread overview]
Message-ID: <20090723130039.GB22626@fieldses.org> (raw)
In-Reply-To: <OF97D5D1D5.E19FBA13-ONC12575FC.002CE971-C12575FC.002D0D78@de.ibm.com>
On Thu, Jul 23, 2009 at 10:12:05AM +0200, Eric Veith wrote:
> Hello,
>
> > I really don't want to enable write delegations until we figure out how
> > to enforce them correctly against local (non-nfs) users of the exported
> > filesystem as well. In addition to breaking delegations on read opens,
> > that means breaking delegations or doing a cb_getattr on operations like
> > stat.
>
> do you know whether there are local FS where the maintainers at least plan
> to incorporate delegations?
Local filesystems don't need support from the filesystem itself; the
only modifications necessary should be to the vfs.
We have patches that do that for read delegations:
http://git.linux-nfs.org/?p=bfields/linux-topics.git;a=shortlog;h=refs/heads/leases
but they still have a few problems. I hope to get them out for review
soon.
Write delegations are more difficult. Distributed filesystems will also
be harder.
--b.
next prev parent reply other threads:[~2009-07-23 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 21:47 nfs4 write delegation status David V. Cloud
[not found] ` <fe2cbb740907211447t4dfcc0dara63bb96648599638-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-22 16:38 ` J. Bruce Fields
2009-07-23 8:12 ` Eric Veith
2009-07-23 13:00 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-23 15:10 Rick Macklem
2009-07-23 18:11 ` Andy Adamson
2009-07-24 18:44 ` J. Bruce Fields
2009-07-24 19:32 ` David V. Cloud
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=20090723130039.GB22626@fieldses.org \
--to=bfields@fieldses.org \
--cc=ERVEITH@de.ibm.com \
--cc=linux-nfs-owner@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox