public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, teigland@redhat.com
Subject: Re: [PATCH] lockd: handle fl_grant callbacks with coalesced locks (RFC)
Date: Tue, 25 Nov 2008 10:12:58 -0500	[thread overview]
Message-ID: <20081125101258.48751871@tleilax.poochiereds.net> (raw)
In-Reply-To: <20081124170653.GF17862@fieldses.org>

On Mon, 24 Nov 2008 12:06:53 -0500
"J. Bruce Fields" <bfields@fieldses.org> wrote:

> 
> I still haven't looked at the code yet.  Probably the first thing I'd
> check would whether the previous code depends on an assumption that each
> grant request results in revisit of exactly one rpc.  I can't see a
> problem.
> 

That's the case with the existing code, since it stops looking for
blocks once it finds a match. The patch I sent changes
nlmsvc_grant_deferred to walk the entire list and set up matching
blocks to be granted.

I think at that point, lockd will rewalk the list (via
nlmsvc_retry_blocked) and revisit each one that got moved to the head
of the list. Please correct me if I'm wrong here though. This code has
a lot of indirection and I'm not sure I fully understand the way
revisits work.

As a side note, one thing that might be nice for this is to have
nlmsvc_grant_deferred to only walk the list of blocks that is
associated with this file. nlm_blocked is an ordered list though, so
I'm not sure whether this might have an effect on "fairness" when
several hosts or processes are contending for the same range.

-- 
Jeff Layton <jlayton@redhat.com>

  reply	other threads:[~2008-11-25 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 21:37 [PATCH] lockd: handle fl_grant callbacks with coalesced locks (RFC) Jeff Layton
2008-11-22  1:15 ` J. Bruce Fields
2008-11-24 15:33   ` Jeff Layton
     [not found]     ` <20081124103313.0c779324-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-11-24 17:06       ` J. Bruce Fields
2008-11-25 15:12         ` Jeff Layton [this message]
2008-12-13 12:40         ` Jeff Layton
     [not found]           ` <20081213074042.2e8223c3-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-12-16 19:38             ` J. Bruce Fields
2008-12-16 19:56               ` J. Bruce Fields
2008-12-16 21:11                 ` Jeff Layton
     [not found]                   ` <20081216161158.2d173667-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-12-17 19:14                     ` David Teigland
2008-12-17 20:01                       ` J. Bruce Fields
2008-12-17 21:28                         ` David Teigland
2009-01-20 23:05                           ` J. Bruce Fields
2009-01-20 23:15                             ` J. Bruce Fields
2009-01-15 16:30                         ` David Teigland
2009-01-19 22:54                           ` David Teigland

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=20081125101258.48751871@tleilax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=teigland@redhat.com \
    /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