public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCHSET 0/2] Cleanup alloc cache init_once handling
Date: Thu, 23 Jan 2025 07:21:10 -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.

 include/linux/io_uring/cmd.h   |  3 ++-
 include/linux/io_uring_types.h |  3 ++-
 io_uring/alloc_cache.h         | 30 +++++++++++++++++++++---------
 io_uring/futex.c               |  4 ++--
 io_uring/io_uring.c            | 13 ++++++++-----
 io_uring/io_uring.h            |  5 ++---
 io_uring/net.c                 | 11 +----------
 io_uring/net.h                 |  7 +++++--
 io_uring/poll.c                |  2 +-
 io_uring/rw.c                  | 10 +---------
 io_uring/rw.h                  |  5 ++++-
 io_uring/uring_cmd.c           | 16 ++++------------
 12 files changed, 53 insertions(+), 56 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-01-23 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 14:21 Jens Axboe [this message]
2025-01-23 14:21 ` [PATCH 1/2] io_uring/uring_cmd: cleanup struct io_uring_cmd_data layout Jens Axboe
2025-01-23 14:38   ` Pavel Begunkov
2025-01-23 14:54     ` Jens Axboe
2025-01-23 14:57       ` Pavel Begunkov
2025-01-23 14:58         ` Jens Axboe
2025-01-23 14:21 ` [PATCH 2/2] io_uring: get rid of alloc cache init_once handling Jens Axboe
2025-01-23 14:27   ` Pavel Begunkov
2025-01-23 14:47     ` Pavel Begunkov
2025-01-23 14:55       ` Jens Axboe
2025-01-23 15:05         ` Pavel Begunkov
2025-01-23 15:09           ` Jens Axboe
2025-01-23 14:54     ` 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