From: Dongsu Park <dongsu.park@profitbricks.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
tytso@mit.edu, Namjae Jeon <namjae.jeon@samsung.com>,
xfs@oss.sgi.com, Ashish Sangwan <a.sangwan@samsung.com>,
linux-fsdevel@vger.kernel.org,
Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] util-linux/fallocate: introduce an option -c to support FALLOC_FL_COLLAPSE_RANGE
Date: Thu, 27 Feb 2014 11:27:05 +0100 [thread overview]
Message-ID: <20140227102704.GB29013@gmail.com> (raw)
In-Reply-To: <20140225193101.GW13647@dastard>
Hi Dave,
On 26.02.2014 06:31, Dave Chinner wrote:
> FYI, we've already got support in xfs_io for collapse-range tests
> inside xfstests.
> http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/cmds/xfsprogs.git;a=commit;h=ca692f162d36c871c9c1b6169136b2c70503f2d8
> There are already several tests that use it.
Thanks for the info!
Dongsu
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-02-27 10:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 5:44 [PATCH RESEND 3/10] ext4: Add support FALLOC_FL_COLLAPSE_RANGE for fallocate Namjae Jeon
2014-02-10 23:34 ` Dave Chinner
2014-02-11 11:59 ` Lukáš Czerner
2014-02-12 2:28 ` Namjae Jeon
2014-02-18 9:05 ` Lukáš Czerner
2014-02-18 9:46 ` Dave Chinner
2014-02-18 9:50 ` Namjae Jeon
2014-02-18 14:30 ` Theodore Ts'o
2014-02-19 1:08 ` Namjae Jeon
2014-02-25 19:08 ` [PATCH] util-linux/fallocate: introduce an option -c to support FALLOC_FL_COLLAPSE_RANGE Dongsu Park
2014-02-25 19:31 ` Dave Chinner
2014-02-27 10:27 ` Dongsu Park [this message]
2014-02-27 3:59 ` Namjae Jeon
2014-02-27 10:35 ` [PATCH v2] util-linux/fallocate: introduce an option -c to support COLLAPSE_RANGE Dongsu Park
2014-04-18 10:52 ` Karel Zak
2014-02-27 9:00 ` [PATCH] util-linux/fallocate: introduce an option -c to support FALLOC_FL_COLLAPSE_RANGE Karel Zak
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=20140227102704.GB29013@gmail.com \
--to=dongsu.park@profitbricks.com \
--cc=a.sangwan@samsung.com \
--cc=david@fromorbit.com \
--cc=lczerner@redhat.com \
--cc=linkinjeon@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=tytso@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).