On 2/22/22 3:57 AM, Dylan Yudaken wrote: > read(2)/write(2) and friends support sequential reads without giving an > explicit offset. The result of these should leave the file with an > incremented offset. > > Add tests for both read and write to check that io_uring behaves > consistently in these scenarios. Expect that if you queue many > reads/writes, and set the IOSQE_IO_LINK flag, that they will behave > similarly to calling read(2)/write(2) in sequence. > > Set IOSQE_ASYNC as well in a set of tests. This exacerbates the problem by > forcing work to happen in different threads to submission. > > Also add tests for not setting IOSQE_IO_LINK, but allow the file offset to > progress past the end of the file. Applied, thanks. -- Jens Axboe
