Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] Doubt about dlm_worker
Date: Fri, 11 Sep 2015 10:19:51 +0800	[thread overview]
Message-ID: <55F23A47.8080805@oracle.com> (raw)
In-Reply-To: <55F16E59.8070006@huawei.com>

On 09/10/2015 07:49 PM, Joseph Qi wrote:
> Hi Junxiao & Sunil,
> Your comments would be appreciated.
> 
> Thanks,
> Joseph
> 
> On 2015/9/6 21:11, Joseph Qi wrote:
>> Comments for dlm_dispatch_work is described below:
>> /* Worker function used during recovery. */
>>
>> But actually dlm_worker is used by 4 types of dlm message workers:
>> 	dlm_assert_master_worker
>> 	dlm_deref_lockres_worker
>> 	dlm_request_all_locks_worker
>> 	dlm_mig_lockres_worker
>>
>> And the first 2 are not dlm recovery related. Moreover, it will send
>> DLM_ASSERT_MASTER_MSG to all other nodes in dlm_assert_master_worker.
>> And it may do a lot of assert master during recovery. In our scenario,
>> it is tens of thousands.
>> This will delay the recovery because dlm_worker is a single thread
>> workqueue and cluster is hanging during dlm recovery.
>> So I doubt if we can move the assert master to a new workqueue or just
>> use a system workqueue.
>> Any suggestions?
Take a look at the code and didn't see an obvious need that these four
worker should be run in order and they use locks to protect. So i think
it's OK to split it out. But better do a good test to avoid this unhide
some bug.

Thanks,
Junxiao.
>>
>>
>> _______________________________________________
>> Ocfs2-devel mailing list
>> Ocfs2-devel at oss.oracle.com
>> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>>
>>
> 
> 

      parent reply	other threads:[~2015-09-11  2:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 13:11 [Ocfs2-devel] [RFC] Doubt about dlm_worker Joseph Qi
2015-09-10 11:49 ` Joseph Qi
2015-09-10 19:18   ` Sunil Mushran
2015-09-11  2:19   ` Junxiao Bi [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=55F23A47.8080805@oracle.com \
    --to=junxiao.bi@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