From: Mark Tinguely <tinguely@sgi.com>
To: jeff.liu@oracle.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfstests: improve test 286 for repeated unwritten/hole extents.
Date: Mon, 09 Jul 2012 10:18:33 -0500 [thread overview]
Message-ID: <4FFAF649.8040504@sgi.com> (raw)
In-Reply-To: <4FF31296.8050406@oracle.com>
On 07/03/12 10:41, Jeff Liu wrote:
> v2->v1.
> * Drop the diff of seq.full.
>
> Signed-off-by: Jie Liu<jeff.liu@oracle.com>
>
> ---
> 286 | 87
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 86 insertions(+), 1 deletions(-)
Looks good. I also perforned a xfs_bmap on the source and destination
files to see the portions that were being detected and copied as data.
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-07-09 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 15:41 [PATCH v2] xfstests: improve test 286 for repeated unwritten/hole extents Jeff Liu
2012-07-09 15:18 ` Mark Tinguely [this message]
2012-07-17 7:18 ` Christoph Hellwig
2012-09-24 21:24 ` Mark Tinguely
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=4FFAF649.8040504@sgi.com \
--to=tinguely@sgi.com \
--cc=jeff.liu@oracle.com \
--cc=xfs@oss.sgi.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