From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] ocfs2/dlm: resend deref to new master if recovery occures
Date: Mon, 24 May 2010 21:54:18 -0700 [thread overview]
Message-ID: <4BFB57FA.3090503@oracle.com> (raw)
In-Reply-To: <20100525025004.GB9173@laptop.us.oracle.com>
On 5/24/2010 7:50 PM, Wengang Wang wrote:
>>> delay deref message if DLM_LOCK_RES_RECOVERING is set (which means
>>> recovery got to the lockres before dlm_thread could), move the
>>> lockres to the end of the purgelist and retry later.
>>>
>
> If you meant checking before sending DEREF, it could cause a high cpu
> useage when there are only the ones in recovery left in the purge list
> until they are recovered. --Is that acceptable?
>
Yea, you are right about the cpu usage. I think the right thing would be
to exit the loop after all locks are traversed once.
> regards,
> wengang.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20100524/d283fc49/attachment.html
next prev parent reply other threads:[~2010-05-25 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 19:48 [Ocfs2-devel] [PATCH 1/1] ocfs2/dlm: resend deref to new master if recovery occures Srinivas Eeda
2010-05-25 2:01 ` Wengang Wang
2010-05-25 2:50 ` Wengang Wang
2010-05-25 4:54 ` Srinivas Eeda [this message]
2010-06-03 16:37 ` [Ocfs2-devel] [PATCH] ocfs2/dlm: cancel the migration or redo deref to recovery master Wengang Wang
-- strict thread matches above, loose matches on Subject: below --
2010-05-25 7:31 [Ocfs2-devel] [PATCH 1/1] ocfs2/dlm: resend deref to new master if recovery occures Wengang Wang
2010-05-25 7:35 ` Wengang Wang
2010-05-24 14:35 Wengang Wang
2010-05-24 14:41 ` Wengang Wang
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=4BFB57FA.3090503@oracle.com \
--to=srinivas.eeda@oracle.com \
--cc=ocfs2-devel@oss.oracle.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).