public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "david m. richter" <richterd@citi.umich.edu>
Cc: bfields@citi.umich.edu, linux-fsdevel@vger.kernel.org
Subject: Re: On setting a lease across a cluster
Date: Fri, 4 Jan 2008 13:18:24 -0700	[thread overview]
Message-ID: <20080104201824.GF20473@parisc-linux.org> (raw)
In-Reply-To: <Pine.BSO.4.64.0801041349110.31957@citi.umich.edu>

On Fri, Jan 04, 2008 at 01:55:36PM -0500, david m. richter wrote:
> 	fwiw, i've done some work on extending the lease subsystem to help 
> support the full range of requirements for NFSv4 file and directory 
> delegations (e.g., breaking a lease when unlinking a file) and we ended up 
> actually doing most of what you've just suggested here, which i take to be 
> a good sign.

As long as it's great minds thinking alike and not fools seldom
differing ;-)

> 	most of my refactoring came out of trying to simplify locking and 
> avoid holding locks too long (rather than specifically focusing on 
> cluster-oriented stuff, but the goals dovetail) and your work on getting 
> the BKL out of locks.c entirely is something i really like and look 
> forward to.

Excellent.  Shall I make the patch myself, or did you want to post a
patch based on working code?  ;-)

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  parent reply	other threads:[~2008-01-04 20:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 18:14 On setting a lease across a cluster Matthew Wilcox
2008-01-04 18:55 ` david m. richter
2008-01-04 19:47   ` J. Bruce Fields
2008-01-04 20:35     ` Matthew Wilcox
2008-01-04 20:53       ` J. Bruce Fields
2008-01-04 21:08         ` Matthew Wilcox
2008-01-04 21:16           ` J. Bruce Fields
2008-01-04 20:18   ` Matthew Wilcox [this message]
2008-01-05 17:44     ` david m. richter

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=20080104201824.GF20473@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=bfields@citi.umich.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=richterd@citi.umich.edu \
    /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