All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: linux-nfs@vger.kernel.org, Pavel Emelyanov <xemul@openvz.org>,
	jlayton@redhat.com
Subject: Re: [NLM] support for a per-mount grace period.
Date: Tue, 23 Aug 2011 10:32:57 -0400	[thread overview]
Message-ID: <20110823143257.GE16261@fieldses.org> (raw)
In-Reply-To: <20110823141909.GA2861@janus>

On Tue, Aug 23, 2011 at 04:19:09PM +0200, Frank van Maarseveen wrote:
> On Fri, Jul 29, 2011 at 01:11:27PM -0400, J. Bruce Fields wrote:
> > On Thu, Jul 28, 2011 at 08:44:18PM +0200, Frank van Maarseveen wrote:
> > > The following two patches implement support for a per-mount NLM
> > > grace period. The first patch is a minor cleanup which pushes
> > > down locks_in_grace() calls into functions shared by NFS[234]. Two
> > > locks_in_grace() tests have been reordered to avoid duplicate calls at
> > > run-time (assuming gcc is smart enough). nlmsvc_grace_period is now a
> > > function instead of an unused variable.
> > > 
> > > The second patch is the actual implementation. It is currently in use for
> > > a number of NFSv3 virtual servers on one physical machine running 2.6.39.3
> > > where the virtualization is based on using different IPv4 addresses.
> > 
> > Thanks, that is something we'd like to have working well.
> 
> Are the patches queued anywhere for inclusion in mainline?

To merge it upstream, at a minimum we need NFSv4 working as well.  It
causes problems when version n+1 lacks features that version n has,
especially in the presence of clients automatically negotiate up.

I'm also inclined to think that making the various data structures and
interfaces network-namespace-dependent is going to result in the cleaner
and more useful solution.

I probably should take that first cleanup patch at least, though.

--b.

  reply	other threads:[~2011-08-23 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 18:44 [NLM] support for a per-mount grace period Frank van Maarseveen
2011-07-28 18:44 ` [PATCH 1/2] Minor NLM cleanup preparing for a per-mount based grace time Frank van Maarseveen
2011-07-28 18:44 ` [PATCH 2/2] Support a per-mount NLM grace period Frank van Maarseveen
2011-07-29 17:11 ` [NLM] support for a per-mount " J. Bruce Fields
2011-07-29 17:40   ` Chuck Lever
2011-07-30  9:44   ` Frank van Maarseveen
2011-08-23 14:19   ` Frank van Maarseveen
2011-08-23 14:32     ` J. Bruce Fields [this message]
2011-08-23 15:49       ` Frank van Maarseveen

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=20110823143257.GE16261@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=frankvm@frankvm.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xemul@openvz.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.