public inbox for [email protected]
 help / color / mirror / Atom feed
From: Zorro Lang <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: [PATCH v2 0/4] fsstress,fsx: add io_uring test and do some fix
Date: Sun,  9 Aug 2020 14:30:36 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

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




             reply	other threads:[~2020-08-09  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09  6:30 Zorro Lang [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox