From: Juan Gomez <juang@us.ibm.com>
To: mike.kupfer@sun.com
Cc: kupfer@athyra.eng.sun.com, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net, trond.myklebust@fys.uio.no
Subject: Re: [NFS] Re: Non-blocking lock requests during the grace period
Date: Tue, 19 Nov 2002 10:06:11 -0800 [thread overview]
Message-ID: <OFB5AB2A91.F36007C8-ON87256C76.00632179@us.ibm.com> (raw)
Mike,
I agree with the F_GETLK part, as I pointed out to Trond earlier. However,
I feel it is odd to block a client for about one minutre when it issues
"non-blocking" lock requests. I have seen that Solaris code does so but
still feels odd and it may conflict with what most programmers expect,
though I see your point, perhaps if this was well documented in man pages
there would not be a problem. In Linux this is not the case.
Juan
|---------+---------------------------->
| | mike.kupfer@sun.c|
| | om |
| | Sent by: |
| | kupfer@athyra.eng|
| | .sun.com |
| | |
| | |
| | 11/18/02 05:04 PM|
| | |
|---------+---------------------------->
>-------------------------------------------------------------------------------------------------------------------------|
| |
| To: trond.myklebust@fys.uio.no |
| cc: Juan Gomez/Almaden/IBM@IBMUS, linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net |
| Subject: Re: [NFS] Re: Non-blocking lock requests during the grace period |
| |
| |
>-------------------------------------------------------------------------------------------------------------------------|
>>>>> "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.
next reply other threads:[~2002-11-19 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 18:06 Juan Gomez [this message]
2002-11-20 18:23 ` Mike Kupfer
-- strict thread matches above, loose matches on Subject: below --
2002-11-15 20:01 Trond Myklebust
2002-11-19 1:04 ` [NFS] " 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=OFB5AB2A91.F36007C8-ON87256C76.00632179@us.ibm.com \
--to=juang@us.ibm.com \
--cc=kupfer@athyra.eng.sun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kupfer@sun.com \
--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®