From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] Ocfs2: Optimize truncting and punching-hole codes.
Date: Thu, 04 Feb 2010 19:35:03 +0800 [thread overview]
Message-ID: <4B6AB0E7.1000505@oracle.com> (raw)
Tao, Joel,
These three patches were for truncate and punching-hole optimization.
1st patch was all about optimization of truncating.
2nd patch was a fixup of bz1216, based on 1st patch
3rd patch was for optimization of punching hole, based on former 2 patches.
#1 and #2 patch has been tested well, should be a somewhat stable
version now,
while #3 patch is a rough v1 one, still needs more tests though simple
comparion test
and sanity check have been done. the reason why I sent it out with
former 2 stable ones
together is just to let it get reviewed earlier.
Joel,
Therefore, you can only merge the first 2 patches if things are in a
hurry.
Regards,
Tristan.
reply other threads:[~2010-02-04 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B6AB0E7.1000505@oracle.com \
--to=tristan.ye@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.