From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] dlm: overlapping cancel and unlock
Date: Wed, 28 Mar 2007 16:40:16 +0100 [thread overview]
Message-ID: <1175096416.1636.73.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20070328145645.GD22230@redhat.com>
Hi,
On Wed, 2007-03-28 at 09:56 -0500, David Teigland wrote:
> Full cancel and force-unlock support. In the past, cancel and force-unlock
> wouldn't work if there was another operation in progress on the lock. Now,
> both cancel and unlock-force can overlap an operation on a lock, meaning there
> may be 2 or 3 operations in progress on a lock in parallel. This support is
> important not only because cancel and force-unlock are explicit operations
> that an app can use, but both are used implicitly when a process exits while
> holding locks.
>
Now pushed to the -nmw git tree. Thanks,
Steve.
next prev parent reply other threads:[~2007-03-28 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 14:56 [Cluster-devel] [PATCH] dlm: overlapping cancel and unlock David Teigland
2007-03-28 15:40 ` Steven Whitehouse [this message]
2007-03-28 16:36 ` Robert Peterson
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=1175096416.1636.73.camel@quoit.chygwyn.com \
--to=swhiteho@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;
as well as URLs for NNTP newsgroup(s).