From: WuBo <wu.bo@cn.fujitsu.com>
To: linux-fsdevel@vger.kernel.org,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>
Subject: [PATCH v2 0/3] xfstests: Add a group of reservation space test
Date: Tue, 08 Nov 2011 11:38:41 +0800 [thread overview]
Message-ID: <4EB8A441.7090506@cn.fujitsu.com> (raw)
Changes v1->v2:
- Make test-set support generic
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 273, I hope it's usefull for Josef's reserve improve work.
For test 274 and 275, the current btrfs is not pass yet.
Wu Bo (3):
xfstests 273: add a copy and reserve test
xfstests 274: add a prealloc and reserve test
xfstests 275: add a write and reserve test
273 | 145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
273.out | 4 ++
274 | 91 +++++++++++++++++++++++++++++++++++++++
274.out | 5 ++
275 | 89 ++++++++++++++++++++++++++++++++++++++
275.out | 5 ++
group | 3 +
7 files changed, 342 insertions(+), 0 deletions(-)
create mode 100755 273
create mode 100644 273.out
create mode 100755 274
create mode 100644 274.out
create mode 100755 275
create mode 100644 275.out
--
1.7.3.1
WARNING: multiple messages have this Message-ID (diff)
From: WuBo <wu.bo@cn.fujitsu.com>
To: linux-fsdevel@vger.kernel.org,
Linux Btrfs <linux-btrfs@vger.kernel.org>,
xfs@oss.sgi.com, Christoph Hellwig <hch@infradead.org>
Subject: [PATCH v2 0/3] xfstests: Add a group of reservation space test
Date: Tue, 08 Nov 2011 11:38:41 +0800 [thread overview]
Message-ID: <4EB8A441.7090506@cn.fujitsu.com> (raw)
Changes v1->v2:
- Make test-set support generic
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 273, I hope it's usefull for Josef's reserve improve work.
For test 274 and 275, the current btrfs is not pass yet.
Wu Bo (3):
xfstests 273: add a copy and reserve test
xfstests 274: add a prealloc and reserve test
xfstests 275: add a write and reserve test
273 | 145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
273.out | 4 ++
274 | 91 +++++++++++++++++++++++++++++++++++++++
274.out | 5 ++
275 | 89 ++++++++++++++++++++++++++++++++++++++
275.out | 5 ++
group | 3 +
7 files changed, 342 insertions(+), 0 deletions(-)
create mode 100755 273
create mode 100644 273.out
create mode 100755 274
create mode 100644 274.out
create mode 100755 275
create mode 100644 275.out
--
1.7.3.1
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-11-08 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 3:38 WuBo [this message]
2011-11-08 3:38 ` [PATCH v2 0/3] xfstests: Add a group of reservation space test WuBo
2011-11-08 3:40 ` [PATCH v2 1/3] xfstests 273: add a copy and reserve test WuBo
2011-11-08 3:40 ` WuBo
2011-11-08 3:41 ` [PATCH v2 2/3] xfstests 274: add a prealloc " WuBo
2011-11-08 3:41 ` WuBo
2011-11-08 3:41 ` [PATCH v2 3/3] xfstests 275: add a write " WuBo
2011-11-08 3:41 ` WuBo
2011-11-09 8:38 ` [PATCH v2 0/3] xfstests: Add a group of reservation space test Christoph Hellwig
2011-11-09 8:38 ` Christoph Hellwig
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=4EB8A441.7090506@cn.fujitsu.com \
--to=wu.bo@cn.fujitsu.com \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.