From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] ocfs2: a method to prevent lock on the blocked queue is starved.
Date: Fri, 25 Sep 2015 09:53:36 +0800 [thread overview]
Message-ID: <5604A920.3040200@huawei.com> (raw)
In-Reply-To: <55DEFE69.2060909@huawei.com>
Simply switch converting list and blocked list cannot resolve the
starvation case fundamentally.
Maybe we have to set a deadline and bring in a scheduler strategy.
@Junxiao, do you have any other idea?
On 2015/8/27 20:11, jiangyiwen wrote:
> In dlm_shuffle_lists, if there are conversions still blocked on the
> converting queue all the time, the blocked locks on the blocked queue
> can never be processed, so the locks on the blocked queue will be
> starved.
>
> So I have an idea to solve this problem: To switch the priority between
> the converting queue and blocked queue, i.e. process the locks on the
> blocked queue first. In this way, the lock on the blocked queue will
> be processed and it will not enter the blocked queue until the
> lockres is purged. so the scenario above will be solved.
>
> Anyone has better ideas or advices?
>
> Thanks,
> Yiwen Jiang
>
>
> .
>
prev parent reply other threads:[~2015-09-25 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 12:11 [Ocfs2-devel] [RFC] ocfs2: a method to prevent lock on the blocked queue is starved jiangyiwen
2015-09-25 1:53 ` Joseph Qi [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=5604A920.3040200@huawei.com \
--to=joseph.qi@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.