From: tytso@mit.edu
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
ext4 development <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>, Giel de Nijs <giel@vectorwise.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 12:25:02 -0500 [thread overview]
Message-ID: <20100130172502.GA788@thunk.org> (raw)
In-Reply-To: <4B645B0D.205@sandeen.net>
On Sat, Jan 30, 2010 at 10:15:09AM -0600, Eric Sandeen wrote:
> > me on a 32-bit machine. The patch below fixes it up, but it seems like
> > we should rather add a variant of that code as aio_read/write commands
> > to xfs_io instead of adding a new test program.
>
> ok, that's probably better - again, though, it takes at least a release
> cycle before most folks can test it. But I guess that's not the end of
> the world.
Stupid question --- who uses xfs_io besides xfstests? Any chance we
could consider dropping in some version of xfs_io into xfstests, or
actually moving it into xfstests from xfsprogs if xfstests is the
exclusive user of that program? I've been trying to get more people
to use xfstests, since it would be good if more companies and more
projects were using it --- and one of the things that makes it hard is
all of the dependencies that it has. If there was some way we could
gradually make xfstests more self-contained, it would certainly be
nice.
- Ted
next prev parent reply other threads:[~2010-01-30 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:05 [PATCH] xfstests 224: test aio hole-fill at 4g Eric Sandeen
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 17:25 ` tytso [this message]
2010-01-30 18:31 ` Eric Sandeen
2010-01-30 19:11 ` Christoph Hellwig
2010-01-30 19:46 ` Eric Sandeen
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=20100130172502.GA788@thunk.org \
--to=tytso@mit.edu \
--cc=giel@vectorwise.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@sandeen.net \
--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).