From: Allison Henderson <achender@linux.vnet.ibm.com>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org, cmm@us.ibm.com
Subject: Re: [PATCH RFC v1 0/5]Factor common code from convert and split unwritten.
Date: Tue, 26 Apr 2011 12:08:52 -0700 [thread overview]
Message-ID: <4DB71844.5030103@linux.vnet.ibm.com> (raw)
In-Reply-To: <1303548259-28311-1-git-send-email-xiaoqiangnk@gmail.com>
On 4/23/2011 1:44 AM, Yongqiang Yang wrote:
> v0->v1:
> fix a bug in ext4_ext_convert_to_initialized() reported by
> Allison<achender@linux.vnet.ibm.com>.
>
> optimize ext4_ext_convert_to_initialized().
>
> -- factor common code
> These patches factor common code from ext4_ext_convert_to_initialized() and
> ext4_split_unwritten_extents() so that extent-move-on-write in snapshot and
> punch hole can be built on the common code.
>
> -- optimization
> the 4th and the 5th patch optimize ext4_ext_convert_to_initialized() by
> zeroing out in memory.
>
>
> [PATCH RFC v1 1/5] ext4:Add a function merging extent right and left.
> [PATCH RFC v1 2/5] ext4:Add two functions splitting an extent.
> [PATCH RFC v1 3/5] ext4:Reimplement convert and split_unwritten.
> [PATCH RFC v1 4/5] ext4: Add a function ext4_ext_zeroout_mem().
> [PATCH RFC v1 5/5] ext4: optimize ext4_ext_convert_to_initialized().
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi there,
Just an update on your patch set. Im am working on getting the punch
hole patch to work with this new set, but I'm am having trouble getting
it through the stress test. It gets up to around 48265 file operations,
and then hangs. So I am currently trying to narrow down the problem. It
looks like it does it with or with out the extra punch hole patches, but
you may need to enable fallocate in the fsx Makefile to recreate the
problem. I will keep you posted if I find any more clues.
Allison Henderson
next prev parent reply other threads:[~2011-04-26 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 8:44 [PATCH RFC v1 0/5]Factor common code from convert and split unwritten Yongqiang Yang
2011-04-23 8:44 ` [PATCH RFC v1 1/5] ext4:Add a function merging extent right and left Yongqiang Yang
2011-04-23 8:44 ` [PATCH RFC v1 2/5] ext4:Add two functions splitting an extent Yongqiang Yang
2011-04-23 8:44 ` [PATCH RFC v1 3/5] ext4:Reimplement convert and split_unwritten Yongqiang Yang
2011-04-23 8:44 ` [PATCH RFC v1 4/5] ext4: Add a function ext4_ext_zeroout_mem() Yongqiang Yang
2011-04-23 8:44 ` [PATCH RFC v1 5/5] ext4: optimize ext4_ext_convert_to_initialized() Yongqiang Yang
2011-04-26 19:08 ` Allison Henderson [this message]
2011-04-27 1:14 ` [PATCH RFC v1 0/5]Factor common code from convert and split unwritten Yongqiang Yang
2011-04-27 4:48 ` Yongqiang Yang
2011-04-27 6:34 ` Allison Henderson
2011-04-27 7:19 ` Yongqiang Yang
2011-04-28 6:05 ` Yongqiang Yang
2011-04-28 19:51 ` Allison Henderson
2011-04-29 19:16 ` Allison Henderson
2011-04-29 19:42 ` Yongqiang Yang
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=4DB71844.5030103@linux.vnet.ibm.com \
--to=achender@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xiaoqiangnk@gmail.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;
as well as URLs for NNTP newsgroup(s).