From: Hao Xu <haoxu.linux@gmail.com>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Pavel Begunkov <asml.silence@gmail.com>
Subject: [PATCH liburing 0/6] liburing changes for multishot accept
Date: Sat, 14 May 2022 22:35:28 +0800 [thread overview]
Message-ID: <20220514143534.59162-1-haoxu.linux@gmail.com> (raw)
This adds two APIs for multishot accept, and some tests for it.
Man page changes as well.
Hao Xu (6):
test/accept.c: close the listen fd at the end of the test
liburing.h: support multishot accept
liburing.h: add api to support multishot accept direct
test/accept.c: add test for multishot mode accept
test/accept.c: test for multishot direct accept with wrong arg
man/io_uring_prep_accept.3: add man info for multishot accept
man/io_uring_prep_accept.3 | 51 ++-
man/io_uring_prep_multishot_accept.3 | 1 +
man/io_uring_prep_multishot_accept_direct.3 | 1 +
src/include/liburing.h | 21 ++
src/include/liburing/io_uring.h | 14 +
test/accept.c | 326 ++++++++++++++++----
6 files changed, 340 insertions(+), 74 deletions(-)
create mode 120000 man/io_uring_prep_multishot_accept.3
create mode 120000 man/io_uring_prep_multishot_accept_direct.3
--
2.36.0
next reply other threads:[~2022-05-14 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 14:35 Hao Xu [this message]
2022-05-14 14:35 ` [PATCH 1/6] test/accept.c: close the listen fd at the end of the test Hao Xu
2022-05-14 14:35 ` [PATCH 2/6] liburing.h: support multishot accept Hao Xu
2022-05-14 14:35 ` [PATCH 3/6] liburing.h: add api to support multishot accept direct Hao Xu
2022-05-14 14:35 ` [PATCH 4/6] test/accept.c: add test for multishot mode accept Hao Xu
2022-05-14 14:35 ` [PATCH 5/6] test/accept.c: test for multishot direct accept with wrong arg Hao Xu
2022-05-14 14:35 ` [PATCH 6/6] man/io_uring_prep_accept.3: add man info for multishot accept Hao Xu
2022-05-14 15:32 ` [PATCH liburing 0/6] liburing changes " Jens Axboe
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=20220514143534.59162-1-haoxu.linux@gmail.com \
--to=haoxu.linux@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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