From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [RFC 0/6] io_uring simplify zerocopy send API
Date: Thu, 1 Sep 2022 09:13:20 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/1/22 4:53 AM, Pavel Begunkov wrote:
> We're changing zerocopy send API making it a bit less flexible but
> much simpler based on the feedback we've got from people trying it
> out. We replace slots and flushing with a per request notifications.
> The API change is described in 5/6 in more details.
> more in 5/6.
>
> The only real functional change is in 5/6, 2-4 are reverts, and patches
> 1 and 6 are fixing selftests.
Let's go for this, we can always bring back notification slots in a
later release if it's deemed necessary or beneficial, however we
can't take it out if we release 6.0 with the change...
--
Jens Axboe
next prev parent reply other threads:[~2022-09-01 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 10:53 [RFC 0/6] io_uring simplify zerocopy send API Pavel Begunkov
2022-09-01 10:54 ` [RFC 1/6] selftests/net: temporarily disable io_uring zc test Pavel Begunkov
2022-09-01 10:54 ` [RFC 2/6] Revert "io_uring: add zc notification flush requests" Pavel Begunkov
2022-09-01 10:54 ` [RFC 3/6] Revert "io_uring: rename IORING_OP_FILES_UPDATE" Pavel Begunkov
2022-09-01 10:54 ` [RFC 4/6] io_uring/notif: remove notif registration Pavel Begunkov
2022-09-01 10:54 ` [RFC 5/6] io_uring/net: simplify zerocopy send user API Pavel Begunkov
2022-09-01 10:54 ` [RFC 6/6] selftests/net: return back io_uring zc send tests Pavel Begunkov
2022-09-01 15:13 ` Jens Axboe [this message]
2022-09-01 15:54 ` [RFC 0/6] io_uring simplify zerocopy send API 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