From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Greg Freemyer <greg.freemyer@gmail.com>,
Eric Sandeen <sandeen@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
hch@lst.de, xfs@oss.sgi.com
Subject: Re: [PATCH 1/6] xfstest: add fio git submodule
Date: Mon, 24 Sep 2012 16:41:42 +0400 [thread overview]
Message-ID: <87r4pr1tkp.fsf@openvz.org> (raw)
In-Reply-To: <CAGpXXZ+LGZcoztAcEND46ndhmGbKHjVmykAU4d11Jsf7B_L53Q@mail.gmail.com>
On Mon, 24 Sep 2012 08:23:04 -0400, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> On Sun, Sep 23, 2012 at 11:16 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> > (I package fio for Fedora, is it not commonly available on other
> > distros?)
>
> opensuse has it in the benchmarking repo, but not in the main release
> repos. If it is getting regular updates and users will want to have
> the latest version, it makes sense for opensuse to leave it that way.
> This discussion may change that.
>
> As of a year ago, xfstests dependencies could all be met from the main
> repos. (see howto http://en.opensuse.org/SDB:XFStests)
>
> I believe a basic set of xfstests is run as part of the QA process for
> every factory build (factory is similar to rawhide). At least it was
> during 12.1 pre-release testing a year ago.
> http://openqa.opensuse.org/results/
>
> Not a huge deal, but having xfstests tests which depend on fio would
> either mean opensuse dropping those tests that depend on fio from its
> routine QA testing, or it would mean adding fio to the main distro.
>
> How far into xfstests is fio likely to integrate? If it is to become
> a core tool and it is not going to be provided by xfstests itself, I
> can try to submit fio to factory. It will just have to kept new
> enough to satisfy xfstests version requirements.
As far as i can say fio potentially can replace most of hardcoded
regression binaries.
>
> I do hope that if the distro has to provide a fio package, then
> xfstests only depend on the version, not the git check-in.
>
> Greg
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-09-24 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a>
2012-09-23 19:24 ` [PATCH 1/6] xfstest: add fio git submodule Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 2/6] xfstest: add configurable load factors Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 3/6] xfstest: allow fsstress to use load factor where appropriate Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 4/6] xfstest add fallocate/truncate vs AIO/DIO stress test Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 5/6] xfstest: add fallocate/punch_hole " Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 6/6] xfstest: add defragmentation stress test for ext4 Dmitry Monakhov
2012-09-24 3:16 ` [PATCH 1/6] xfstest: add fio git submodule Eric Sandeen
2012-09-24 10:03 ` Dmitry Monakhov
2012-09-24 11:37 ` Dave Chinner
2012-09-24 12:38 ` Dmitry Monakhov
2012-09-24 13:53 ` Dave Chinner
2012-09-24 12:23 ` Greg Freemyer
2012-09-24 12:41 ` Dmitry Monakhov [this message]
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=87r4pr1tkp.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=greg.freemyer@gmail.com \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).