linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Henderson <achender@linux.vnet.ibm.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: XFS Add Punch Hole Testing to FSX
Date: Mon, 02 May 2011 12:16:12 -0700	[thread overview]
Message-ID: <4DBF02FC.9080608@linux.vnet.ibm.com> (raw)

Hi all,

This is the fsx test I have been using to develop punch hole for ext4. 
There have been some requests to see it, so I will send it to both 
linux-fsdevl and the ext4 mailing list.

Ext4 punch hole is done through fallocate, so the patch adds the punch 
hole flag to fallocate test.  Initially I had trouble enabling the 
existing fallocate tests until I made a fix to the Makefile.  It looks 
like it should be checking for HAVE_FALLOCATE equal to "yes" instead of 
"true"?  Im not sure if that was a bug or if there was something else I 
was supposed to do to configure it correctly, so feed back is 
appreciated :)  Thanks all!

Allison Henderson

                 reply	other threads:[~2011-05-02 19:16 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=4DBF02FC.9080608@linux.vnet.ibm.com \
    --to=achender@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).