From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Reused freed extent block in b-tree operation.
Date: Thu, 19 Mar 2009 15:13:00 -0700 [thread overview]
Message-ID: <20090319221300.GC18943@mail.oracle.com> (raw)
In-Reply-To: <1237415178-15075-1-git-send-email-tao.ma@oracle.com>
On Thu, Mar 19, 2009 at 06:26:18AM +0800, Tao Ma wrote:
> Hi all,
> This is the patch for the RFC. I have tested it in my ppc
> box, it works OK.
>
> In some b-tree operations we may have the chance that we haven't
> reserved any metadata at the beginning because we think we don't
> need. While the 1st operation free a extent block while the 2nd
> operation need one. Our current code can't handle this. So this
> patch try to re-use the freed extent block so that we can pass
> the scenario above. For more details about the bug, see
>
> [RFC] metadata alloc fix in machines which has PAGE_SIZE > CLUSTER_SIZE
> http://oss.oracle.com/pipermail/ocfs2-devel/2009-March/004185.html.
>
> Signed-off-by: Tao Ma <tao.ma@oracle.com>
This looks sane to me, but I'd like Mark's opinion as well. He
knows the tree code better than I do.
Joel
--
Life's Little Instruction Book #274
"Leave everything a little better than you found it."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-03-19 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 13:57 [Ocfs2-devel] [RFC] metadata alloc fix in machines which has PAGE_SIZE > CLUSTER_SIZE Tao Ma
2009-03-18 22:26 ` [Ocfs2-devel] [PATCH] ocfs2: Reused freed extent block in b-tree operation Tao Ma
2009-03-19 22:13 ` Joel Becker [this message]
2009-03-20 0:30 ` [Ocfs2-devel] [RFC] metadata alloc fix in machines which has PAGE_SIZE > CLUSTER_SIZE Mark Fasheh
2009-03-20 0:41 ` Tao Ma
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=20090319221300.GC18943@mail.oracle.com \
--to=joel.becker@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 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.