mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mike.kupfer@sun.com
To: trond.myklebust@fys.uio.no
Cc: Juan Gomez <juang@us.ibm.com>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: Non-blocking lock requests during the grace period
Date: Mon, 18 Nov 2002 17:04:32 -0800	[thread overview]
Message-ID: <200211190104.gAJ14Wf9136218@athyra.eng.sun.com> (raw)
In-Reply-To: Your message of "Fri, 15 Nov 2002 21:01:21 +0100." <15829.21137.152716.652146@helicity.uio.no>

>>>>> "Trond" == Trond Myklebust <trond.myklebust@fys.uio.no> writes:

>>>>> " " == Juan Gomez <juang@us.ibm.com> writes:

    >> (note that F_GETLK man page does not provide EAGAIN as a
    >> possible error code).

F_GETLK indicates a conflict by changing the arg struct to show the
conflicting lock.

As for the original topic, I would hesitate before changing the client
locking code to return EAGAIN just because the server is in its grace
period.  The "blocking" or "non-blocking" behavior is tied to what
happens when there is already a lock that conflicts with the requested
one.  When the server is in the grace period, it's unknown as to
whether there is already a lock that conflicts with the requested
one.

Mike Kupfer				mike.kupfer@sun.com
Solaris File Sharing			Speaking for myself, not for Sun.



  reply	other threads:[~2002-11-19  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 19:09 Juan Gomez
2002-11-15 20:01 ` Trond Myklebust
2002-11-19  1:04   ` mike.kupfer [this message]
2002-11-19 18:06 [NFS] " Juan Gomez
2002-11-20 18:23 ` Mike Kupfer

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=200211190104.gAJ14Wf9136218@athyra.eng.sun.com \
    --to=mike.kupfer@sun.com \
    --cc=juang@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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

all inboxes | Powered by JetHome®