public inbox for [email protected]
 help / color / mirror / Atom feed
* [PATCH v2 0/4] fsstress,fsx: add io_uring test and do some fix
@ 2020-08-09  6:30 Zorro Lang
  2020-08-09  6:30 ` [PATCH v2 1/4] fsstress: add IO_URING read and write operations Zorro Lang
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Zorro Lang @ 2020-08-09  6:30 UTC (permalink / raw)
  To: fstests; +Cc: io-uring, jmoyer

This patchset tries to add new IO_URING test into fsstress [1/4] and fsx [4/4].
And then do some changes and bug fix by the way [2/4 and 3/4].

fsstress and fsx are important tools in xfstests to do filesystem I/Os test,
lots of test cases use it. So add IO_URING operation into fsstress and fsx
will help to cover IO_URING test from fs side.

I'm not an IO_URING expert, so cc io-uring@ list, please feel free to
tell me if you find something wrong or have any suggestions to improve
the test.

V2 did below changes:
1) 1/4 change the definition of URING_ENTRIES to 1
2) 2/4 change the difinition of AIO_ENTRIES to 1, undo an unrelated changed line
3) 4/4 turn to use io_uring_prep_readv/io_uring_prep_writev, due to old
       liburing(0.2-2) doesn't support io_uring_prep_read/io_uring_prep_write.

Thanks,
Zorro




^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2020-08-22 18:05 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-08-09  6:30 [PATCH v2 0/4] fsstress,fsx: add io_uring test and do some fix Zorro Lang
2020-08-09  6:30 ` [PATCH v2 1/4] fsstress: add IO_URING read and write operations Zorro Lang
2020-08-09 17:51   ` Jens Axboe
2020-08-22 18:14     ` Zorro Lang
2020-08-22 18:05       ` Jens Axboe
2020-08-09  6:30 ` [PATCH v2 2/4] fsstress: reduce the number of events when io_setup Zorro Lang
2020-08-09  6:30 ` [PATCH v2 3/4] fsstress: fix memory leak in do_aio_rw Zorro Lang
2020-08-09  6:30 ` [PATCH v2 4/4] fsx: add IO_URING test Zorro Lang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox