public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com, csander@purestorage.com
Subject: [PATCHSET v4 0/5] Allow non-atomic allocs for overflows
Date: Sat, 17 May 2025 05:42:10 -0600	[thread overview]
Message-ID: <20250517114938.533378-1-axboe@kernel.dk> (raw)

Hi,

This is heavily inspired by the series that Pavel posted here:

https://lore.kernel.org/io-uring/cover.1747209332.git.asml.silence@gmail.com/

Basically this patchset tries to accomplish two things:

1) Enable GFP_KERNEL alloc of the overflow entries, when possible.

2) Make the overflow side pollute the fast/common path as little as
   possible.

Also does some cleanups, like passing more appropriate and easily
readable arguments to the overflow handling, rather than need 3..5
arguments of various user_data/res/cflags/extra1/extra1 being passed
along.

 include/linux/io_uring_types.h |  2 +-
 io_uring/io_uring.c            | 99 ++++++++++++++++++++++------------
 2 files changed, 65 insertions(+), 36 deletions(-)

Since v3:
- Fix typos in commit message.
- Rename io_cqe_overflow_lockless() -> io_cqe_overflow(), and
  io_cqe_overflow() -> io_cqe_overflow_locked().
- Make io_init_cqe() a static inline function rather than a macro.

-- 
Jens Axboe


             reply	other threads:[~2025-05-17 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 11:42 Jens Axboe [this message]
2025-05-17 11:42 ` [PATCH 1/5] io_uring: open code io_req_cqe_overflow() Jens Axboe
2025-05-17 11:42 ` [PATCH 2/5] io_uring: split alloc and add of overflow Jens Axboe
2025-05-17 23:30   ` Caleb Sander Mateos
2025-05-18  0:48     ` Jens Axboe
2025-05-17 11:42 ` [PATCH 3/5] io_uring: make io_alloc_ocqe() take a struct io_cqe pointer Jens Axboe
2025-05-17 23:28   ` Caleb Sander Mateos
2025-05-17 11:42 ` [PATCH 4/5] io_uring: pass in struct io_big_cqe to io_alloc_ocqe() Jens Axboe
2025-05-17 11:42 ` [PATCH 5/5] io_uring: add new helpers for posting overflows Jens Axboe
2025-05-17 23:32   ` Caleb Sander Mateos

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 \
    --in-reply-to=20250517114938.533378-1-axboe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    /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