From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH 0/6] bunch of zerocopy send changes
Date: Wed, 24 Aug 2022 13:07:37 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
4/6 adds some ordering guarantees for send vs notif CQEs.
5 and 6 save address (if any) when it goes async, so we're more
consistent and don't read it twice.
Pavel Begunkov (6):
io_uring/net: fix must_hold annotation
io_uring/net: fix zc send link failing
io_uring/net: fix indention
io_uring/notif: order notif vs send CQEs
io_uring: conditional ->async_data allocation
io_uring/net: save address for sendzc async execution
io_uring/io_uring.c | 7 +++---
io_uring/net.c | 55 ++++++++++++++++++++++++++++++++++++++-------
io_uring/net.h | 1 +
io_uring/notif.c | 8 ++++---
io_uring/opdef.c | 4 +++-
io_uring/opdef.h | 2 ++
6 files changed, 62 insertions(+), 15 deletions(-)
--
2.37.2
next reply other threads:[~2022-08-24 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 12:07 Pavel Begunkov [this message]
2022-08-24 12:07 ` [PATCH 1/6] io_uring/net: fix must_hold annotation Pavel Begunkov
2022-08-24 12:07 ` [PATCH 2/6] io_uring/net: fix zc send link failing Pavel Begunkov
2022-08-24 12:07 ` [PATCH 3/6] io_uring/net: fix indention Pavel Begunkov
2022-08-24 12:07 ` [PATCH 4/6] io_uring/notif: order notif vs send CQEs Pavel Begunkov
2022-08-24 12:07 ` [PATCH 5/6] io_uring: conditional ->async_data allocation Pavel Begunkov
2022-08-24 12:07 ` [PATCH 6/6] io_uring/net: save address for sendzc async execution Pavel Begunkov
2022-08-24 14:57 ` [PATCH 0/6] bunch of zerocopy send 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