[LTP] [PATCH v6] Refactor aiocp using new LTP API

Petr Vorel pvorel@suse.cz
Thu Aug 11 11:42:42 CEST 2022

Hi all,

> Hi!
> > Yes, we can reduce the amount of time to generate file (especially if 
> > it's really big), but I wouldn't
> > introduce any repetition because we would like to check that file has 
> > been copied properly during
> > callbacks which are asynchronous by definition.

> I guess that we can do a little trick such as making the buffer with
> random data slightly bigger and choosing a random start offset in that
> etc.

I tested Andreas patches from v2 to v6 and aiocp with -f DIRECT works only on
btrfs. Running on $TMPDIR being on ext4, xfs, tmpfs endup with EINVAL:

# ./aiocp -b 1k -n 1 -f DIRECT
aiocp.c:240: TINFO: Maximum AIO blocks: 65536
aiocp.c:265: TINFO: Fill srcfile.bin with random data
aiocp.c:267: TBROK: open(srcfile.bin,16450,0666) failed: EINVAL (22)

Any idea what could be wrong?

Kind regards,

More information about the ltp mailing list