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 0/3] fsstress: add io_uring test and do some fix
Date: Thu, 16 Jul 2020 00:07:52 +0800	[thread overview]
Message-ID: <[email protected]> (raw)

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

fsstress is an important tool in xfstests to do random filesystem I/Os
test, lots of test cases use it. So add IO_URING operation into fsstress
will help to make lots of test cases cover IO_URING test naturally.

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.

Thanks,
Zorro




             reply	other threads:[~2020-07-15 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 16:07 Zorro Lang [this message]
2020-07-15 16:07 ` [PATCH 1/3] fsstress: add IO_URING read and write operations Zorro Lang
2020-07-15 16:07 ` [PATCH 2/3] fsstress: reduce the number of events when io_setup Zorro Lang
2020-07-15 16:07 ` [PATCH 3/3] fsstress: fix memory leak in do_aio_rw 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