Re: [PATCH V5 00/30] loop: Issue O_DIRECT aio using bio_vec

From: Dave Chinner
Date: Sun Jan 20 2013 - 17:26:30 EST


On Fri, Jan 18, 2013 at 12:16:35PM -0500, Jeff Moyer wrote:
> Dave Kleikamp <dave.kleikamp@xxxxxxxxxx> writes:
>
> > This patchset was begun by Zach Brown and was originally submitted for
> > review in October, 2009. Feedback was positive, and I have picked up
> > where he left off, porting his patches to the latest mainline kernel
> > and adding support more file systems.
>
> [snip]
>
> > My hopes are that this patchset is finally ready for linux-next.
>
> Hi, Shaggy,
>
> I'm finally getting around to testing this using xfstests. This is my
> setup:
>
> dd if=/dev/zero of=testdev.img bs=1M count=1024
> dd if=/dev/zero of=scratchdev.img bs=1M count=1024
> losetup -f ./testdev.img
> losetup -f ./scratchdev.img
> mkfs -t xfs /dev/loop0
> mount /dev/loop0 /mnt/test
> export TEST_DIR=/mnt/test
> export TEST_DEV=/dev/loop0
> export SCRATCH_MNT=/mnt/scratch
> export SCRATCH_DEV=/dev/loop1
>
> I then ran:
>
> ./check -g aio
>
> and here is the summary:
>
> Ran: 112 113 198 207 208 209 210 211 212 239 240
> Failures: 112 198 207 239 240
> Failed 5 of 11 tests

There's no need to limit xfstests to the aio group here. If the loop
device is what you are actually testing, then you probably want to
run the auto/quick groups as they will do a whole lot more than just
data IO to the loop devices...

Cheers,

Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/