Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Norton.Zhu <norton.zhu@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] ocfs2: Idea to make ocfs2_search_chain high efficiency
Date: Mon, 24 Aug 2015 20:30:35 +0800	[thread overview]
Message-ID: <55DB0E6B.2000606@huawei.com> (raw)

In ocfs2_search_chain, I found it has low efficiency  while searching an available gd in some circumstances:
1) The lun has a great many gd(it reads lots of unavailable gd(free bits is zero));
2) Not too many gd, but the available gd is scattered in the unavailable gd(fragmentation);

So I have an idea to optimize the search method:
1) Use the reserved member in the ocfs2_group_desc to make an available chain list(gds in the list are all available, free bits more than zero);
2) At the beginning, the chain list is the same with origin chain list;
3) While do allocation, it searches gd in the available chain list;
4) After each allocation, if some gd's free bits is zero, Remove it from the available chain list;
5) After each reclaim, if some gd's free bits change from zero to positive, Append it to the head of the available chain list;

Once started with the basics outlined above, no unavailable gd will be read.

Anyone has better ideas or advices?

             reply	other threads:[~2015-08-24 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 12:30 Norton.Zhu [this message]
2015-08-24 16:57 ` [Ocfs2-devel] [RFC] ocfs2: Idea to make ocfs2_search_chain high efficiency Srinivas Eeda
2015-08-25  1:47   ` Joel Becker
2015-08-25 12:08     ` Norton.Zhu
2015-08-25 18:49 ` Tariq Saeed

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=55DB0E6B.2000606@huawei.com \
    --to=norton.zhu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox