From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCHSET v2 0/3] Cleanup alloc cache init_once handling
Date: Thu, 23 Jan 2025 11:45:24 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
A minor prep patch cleaning up some confusion on types for uring_cmd,
which don't matter now, but will after patch 2. Patch 2 gets rid of
the init_once, and has the cache init functions pass in the number of
bytes to clear for a fresh allocation.
Since v1:
- Make the iovec caching play nice with KASAN. We just free it now,
as even basic KASAN will stomp on this memory. This should also fix
the reported issue with KASAN_EXTRA_INFO and msghdr on the net side
without needing KASAN changes.
- Cleanup the uring_cmd bits, we don't need to retain anything there.
- Use struct_group() for the rw and net bits.
- Add patch killing the _nocache() helper, just allow passing in a
NULL cache for those two cases.
include/linux/io_uring/cmd.h | 2 +-
include/linux/io_uring_types.h | 3 ++-
io_uring/alloc_cache.h | 43 +++++++++++++++++++++++++++-------
io_uring/futex.c | 4 ++--
io_uring/io_uring.c | 12 ++++++----
io_uring/io_uring.h | 21 +++++++----------
io_uring/net.c | 28 +++++-----------------
io_uring/net.h | 20 +++++++++-------
io_uring/poll.c | 2 +-
io_uring/rw.c | 27 +++++----------------
io_uring/rw.h | 27 ++++++++++++---------
io_uring/timeout.c | 2 +-
io_uring/uring_cmd.c | 17 ++++----------
io_uring/waitid.c | 2 +-
14 files changed, 102 insertions(+), 108 deletions(-)
next reply other threads:[~2025-01-23 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 18:45 Jens Axboe [this message]
2025-01-23 18:45 ` [PATCH 1/3] io_uring/uring_cmd: cleanup struct io_uring_cmd_data layout Jens Axboe
2025-01-23 18:45 ` [PATCH 2/3] io_uring: get rid of alloc cache init_once handling Jens Axboe
2025-01-23 19:47 ` Gabriel Krisman Bertazi
2025-01-23 18:45 ` [PATCH 3/3] io_uring/alloc_cache: get rid of _nocache() helper 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