On Tue, 2007-05-08 at 12:50 +1000, David Chinner wrote:
> On Mon, May 07, 2007 at 01:56:23PM -0700, Mingming Cao wrote:
> > In any case, it would be useful to add a new set of testsuites for the
> > new fallocate() syscall and fsstress in LTP testsuites to automatically
> > the preallocation code in ext4/XFS.
>
> I hacked an existing XFS test prog to do manual testing of the fallocate()
> syscall. In the XFSQA suite we have various pre-alloc enhanced utils (e.g.
> fsstress, fsx, etc) that we should probably update to be able to use both
> fallocate and xfsctl so we can test both.
>
> Here's all the programs we use that have preallocation awareness:
>
> chook 982% grep RESVSP ltp/*.c | awk '/^ltp/ { split($1,a,":"); print a[1] ;}' | uniq
> ltp/doio.c
> ltp/fsstress.c
> ltp/fsx.c
> ltp/growfiles.c
> ltp/iogen.c
> chook 983% grep RESVSP src/* | awk '/^src/ { split($1,a,":"); print a[1] ;}' | uniq
> src/alloc.c
> src/fstest.c
> src/iopat.c
> src/randholes.c
> src/resvtest.c
> src/unwritten_mmap.c
> src/unwritten_sync.c
>
Thanks for sharing the info. I think Amit used a fsx version with
preallocation awareness test, but I don't know if we have other ltp
tests that aware preallocation. I would very appreciate if you could
share your preallocation test with us.
> BTW, have you guys tested mmap writes into unwritten extents? ;)
>
I am not sure, Amit, have you done some mmap write test into
uninitialized extents?
Sorry, I still not quite clear what's the mapped problem you are worry
about. Could you explain to me a bit more? thanks!
Mingming
> Cheers,
>
> Dave.
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
