From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH 0/8] legacy provided buffer deprecation / deoptimisation
Date: Wed, 5 Feb 2025 11:36:41 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Legacy provided buffers are slow and discouraged, users are encouraged
to use ring provided buffers instead. Clean up the legacy code, remove
caching and optimisations. The goal here it to make it simpler and less
of a burden to maintain.
Pavel Begunkov (8):
io_uring/kbuf: remove legacy kbuf bulk allocation
io_uring/kbuf: remove legacy kbuf kmem cache
io_uring/kbuf: move locking into io_kbuf_drop()
io_uring/kbuf: simplify __io_put_kbuf
io_uring/kbuf: remove legacy kbuf caching
io_uring/kbuf: open code __io_put_kbuf()
io_uring/kbuf: introduce io_kbuf_drop_legacy()
io_uring/kbuf: uninline __io_put_kbufs
include/linux/io_uring_types.h | 3 -
io_uring/io_uring.c | 11 +--
io_uring/io_uring.h | 1 -
io_uring/kbuf.c | 172 +++++++++++++++------------------
io_uring/kbuf.h | 100 +++----------------
5 files changed, 89 insertions(+), 198 deletions(-)
--
2.47.1
next reply other threads:[~2025-02-05 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 11:36 Pavel Begunkov [this message]
2025-02-05 11:36 ` [PATCH 1/8] io_uring/kbuf: remove legacy kbuf bulk allocation Pavel Begunkov
2025-02-05 11:36 ` [PATCH 2/8] io_uring/kbuf: remove legacy kbuf kmem cache Pavel Begunkov
2025-02-05 11:36 ` [PATCH 3/8] io_uring/kbuf: move locking into io_kbuf_drop() Pavel Begunkov
2025-02-05 11:36 ` [PATCH 4/8] io_uring/kbuf: simplify __io_put_kbuf Pavel Begunkov
2025-02-05 11:36 ` [PATCH 5/8] io_uring/kbuf: remove legacy kbuf caching Pavel Begunkov
2025-02-05 11:36 ` [PATCH 6/8] io_uring/kbuf: open code __io_put_kbuf() Pavel Begunkov
2025-02-05 11:36 ` [PATCH 7/8] io_uring/kbuf: introduce io_kbuf_drop_legacy() Pavel Begunkov
2025-02-05 11:36 ` [PATCH 8/8] io_uring/kbuf: uninline __io_put_kbufs Pavel Begunkov
2025-02-05 16:17 ` [PATCH 0/8] legacy provided buffer deprecation / deoptimisation 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] \
/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