From: Jiaju Zhang <jjzhang.linux@gmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [RFC]Drop unused plock resource when no other plock request comes
Date: Wed, 26 Aug 2009 14:54:11 +0800 [thread overview]
Message-ID: <f8c992a30908252354r12046e98q148d38eba147e1f4@mail.gmail.com> (raw)
In-Reply-To: <20090825153503.GA24475@redhat.com>
On Tue, Aug 25, 2009 at 11:35 PM, David Teigland <teigland@redhat.com>wrote:
> On Tue, Aug 25, 2009 at 11:10:03AM +0800, Jiaju Zhang wrote:
> > On Mon, Aug 24, 2009 at 10:31 PM, David Teigland <teigland@redhat.com
> >wrote:
> >
> > >
> > > You're correct; yes the daemon could easily be changed to drop
> resources
> > > when
> > > there's no locking activity. We'd just set a poll timeout when
> > > plock_resources is non-empty and call drop_resources() if it times out.
> > >
> > > (If you simply want to work around this, you can write a little program
> to
> > > lock a file on the fs to trigger the drop.)
> > >
> > > Dave
> >
> >
> > Many thanks for your guidance :-)
> > So I write a patch to try to fix this. Review and comments are welcome.
>
> Thanks, that looks like it would do the job, but the code is a little
> complicated. Here's a simpler patch, I've not tried it so it may not work
> :)
>
The code is so elegant and it works fine :)
Thanks,
Jiaju
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/cluster-devel/attachments/20090826/bee575bd/attachment.htm>
prev parent reply other threads:[~2009-08-26 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 9:00 [Cluster-devel] [RFC]Drop unused plock resource when no other plock request comes Jiaju Zhang
2009-08-24 14:31 ` [Cluster-devel] " David Teigland
2009-08-25 3:10 ` Jiaju Zhang
2009-08-25 15:35 ` David Teigland
2009-08-26 6:54 ` Jiaju Zhang [this message]
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=f8c992a30908252354r12046e98q148d38eba147e1f4@mail.gmail.com \
--to=jjzhang.linux@gmail.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).