From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH liburing 0/4] zc changes
Date: Wed, 21 Sep 2022 12:21:54 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
We're decoupling notifications generation from whether the request
failed or not. Adjust the tests, so nobody is confused reading it,
and put a note in man.
Also, 4/4 adds a test for just sent zc sendmsg.
Pavel Begunkov (4):
examples: fix sendzc notif handling
test: fix zc tests
man: note about notification generation
tests: add sendmsg_zc tests
examples/send-zerocopy.c | 17 +++---
man/io_uring_enter.2 | 5 +-
src/include/liburing/io_uring.h | 1 +
test/send-zerocopy.c | 101 ++++++++++++++++++++++++--------
4 files changed, 88 insertions(+), 36 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-21 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 11:21 Pavel Begunkov [this message]
2022-09-21 11:21 ` [PATCH liburing 1/4] examples: fix sendzc notif handling Pavel Begunkov
2022-09-21 11:21 ` [PATCH liburing 2/4] test: fix zc tests Pavel Begunkov
2022-09-21 11:21 ` [PATCH liburing 3/4] man: note about notification generation Pavel Begunkov
2022-09-21 11:21 ` [PATCH liburing 4/4] tests: add sendmsg_zc tests Pavel Begunkov
2022-09-21 15:00 ` [PATCH liburing 0/4] zc 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 \
[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