From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH for-next 0/7] small zc improvements
Date: Fri, 4 Nov 2022 10:59:39 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Remove some cycles in a couple of places for zc sends. Touches a bunch of
bits here and there but the main theme is adding additional set of callbacks
for slower path and move in there some optional features.
Pavel Begunkov (7):
io_uring: move kbuf put out of generic tw complete
io_uring/net: remove extra notif rsrc setup
io_uring/net: preset notif tw handler
io_uring/net: rename io_uring_tx_zerocopy_callback
io_uring/net: inline io_notif_flush()
io_uring: move zc reporting from the hot path
io_uring/net: move mm accounting to a slower path
io_uring/io_uring.c | 6 -----
io_uring/net.c | 25 +++++++++++++-------
io_uring/notif.c | 57 ++++++++++++++++++++++++---------------------
io_uring/notif.h | 12 +++++++++-
io_uring/rw.c | 6 +++++
5 files changed, 64 insertions(+), 42 deletions(-)
--
2.38.0
next reply other threads:[~2022-11-04 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 10:59 Pavel Begunkov [this message]
2022-11-04 10:59 ` [PATCH for-next 1/7] io_uring: move kbuf put out of generic tw complete Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 2/7] io_uring/net: remove extra notif rsrc setup Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 3/7] io_uring/net: preset notif tw handler Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 4/7] io_uring/net: rename io_uring_tx_zerocopy_callback Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 5/7] io_uring/net: inline io_notif_flush() Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 6/7] io_uring: move zc reporting from the hot path Pavel Begunkov
2022-11-04 10:59 ` [PATCH for-next 7/7] io_uring/net: move mm accounting to a slower path Pavel Begunkov
2022-11-05 15:20 ` [PATCH for-next 0/7] small zc improvements 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