From: Zorro Lang <zlang@redhat.com> To: fstests@vger.kernel.org Cc: io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH 2/3] fsstress: reduce the number of events when io_setup Date: Thu, 16 Jul 2020 00:07:54 +0800 [thread overview] Message-ID: <20200715160755.14392-3-zlang@redhat.com> (raw) In-Reply-To: <20200715160755.14392-1-zlang@redhat.com> The original number(128) of aio events for io_setup is a little big. When try to run lots of fsstress processes(e.g. -p 1000) always hit io_setup EAGAIN error, due to the nr_events exceeds the limit of available events. So reduce it from 128 to 64, to make more fsstress processes can do AIO test. Signed-off-by: Zorro Lang <zlang@redhat.com> --- ltp/fsstress.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/ltp/fsstress.c b/ltp/fsstress.c index 388ace50..a11206d4 100644 --- a/ltp/fsstress.c +++ b/ltp/fsstress.c @@ -28,6 +28,7 @@ #endif #ifdef AIO #include <libaio.h> +#define AIO_ENTRIES 64 io_context_t io_ctx; #endif #ifdef URING @@ -699,8 +700,8 @@ int main(int argc, char **argv) } procid = i; #ifdef AIO - if (io_setup(128, &io_ctx) != 0) { - fprintf(stderr, "io_setup failed"); + if (io_setup(AIO_ENTRIES, &io_ctx) != 0) { + fprintf(stderr, "io_setup failed\n"); exit(1); } #endif @@ -714,7 +715,7 @@ int main(int argc, char **argv) doproc(); #ifdef AIO if(io_destroy(io_ctx) != 0) { - fprintf(stderr, "io_destroy failed"); + fprintf(stderr, "io_destroy failed\n"); return 1; } #endif -- 2.20.1
next prev parent 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 [PATCH 0/3] fsstress: add io_uring test and do some fix Zorro Lang 2020-07-15 16:07 ` [PATCH 1/3] fsstress: add IO_URING read and write operations Zorro Lang 2020-07-15 16:07 ` Zorro Lang [this message] 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 \ --in-reply-to=20200715160755.14392-3-zlang@redhat.com \ --to=zlang@redhat.com \ --cc=fstests@vger.kernel.org \ --cc=io-uring@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --subject='Re: [PATCH 2/3] fsstress: reduce the number of events when io_setup' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).