From: WuBo <wu.bo@cn.fujitsu.com>
To: linux-fsdevel@vger.kernel.org,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
xfs@oss.sgi.com
Subject: [PATCH 0/3] xfstests: Add a group of reservation space test
Date: Thu, 03 Nov 2011 11:05:41 +0800 [thread overview]
Message-ID: <4EB20505.7070005@cn.fujitsu.com> (raw)
This patch set add a group of reservation space test. Especailly for btrfs.
It includes three parts: copy workload, prealloc and write posix.
For test 264, I hope it's usefull for Josef's reserve improve work.
For test 265 and 266, the current btrfs is not pass yet.
TO avoid fill the huge disk, I just resize the filesystem size which NOT
all filesystems supportted. Here I just make these tests support btrfs only,
but it's can ream to ext3/4 if needed.
Wu Bo (3):
xfstests 264: add a copy and reserve test
xfstests 265: add a prealloc and reserve test
xfstests 266: add a write and reserve test
264 | 158 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
264.out | 6 ++
265 | 107 ++++++++++++++++++++++++++++++++++++++++++
265.out | 5 ++
266 | 104 +++++++++++++++++++++++++++++++++++++++++
266.out | 5 ++
group | 3 +
7 files changed, 388 insertions(+), 0 deletions(-)
create mode 100755 264
create mode 100644 264.out
create mode 100755 265
create mode 100644 265.out
create mode 100755 266
create mode 100644 266.out
--
1.7.3.1
next reply other threads:[~2011-11-03 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 3:05 WuBo [this message]
2011-11-03 3:08 ` [PATCH 1/3] xfstests 264: add a copy and reserve test WuBo
2011-11-03 6:55 ` Christoph Hellwig
2011-11-03 8:04 ` WuBo
2011-11-03 3:09 ` [PATCH 2/3] xfstests 265: add a prealloc " WuBo
2011-11-15 18:21 ` Ben Myers
2011-11-15 19:08 ` Christoph Hellwig
2011-11-16 1:30 ` WuBo
2011-11-03 3:09 ` [PATCH 3/3] xfstests 266: add a write " WuBo
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=4EB20505.7070005@cn.fujitsu.com \
--to=wu.bo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).