public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH v2 0/7] simplify overflow CQE handling
Date: Sat, 17 May 2025 13:27:36 +0100	[thread overview]
Message-ID: <cover.1747483784.git.asml.silence@gmail.com> (raw)

Some improvements for overflow posting like replacing GFP_ATOMIC
with GFP_KERNEL in few cases and debug assertions for invariant
violations.

v2: nest another lock to get rid of conditional locking

Pavel Begunkov (7):
  io_uring: fix overflow resched cqe reordering
  io_uring: init overflow entry before passing to tracing
  io_uring: open code io_req_cqe_overflow()
  io_uring: split __io_cqring_overflow_flush()
  io_uring: separate lock for protecting overflow list
  io_uring: avoid GFP_ATOMIC for overflows if possible
  io_uring: add lockdep warning for overflow posting

 include/linux/io_uring_types.h |   1 +
 io_uring/io_uring.c            | 122 ++++++++++++++++++---------------
 2 files changed, 67 insertions(+), 56 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-17 12:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 12:27 Pavel Begunkov [this message]
2025-05-17 12:27 ` [PATCH v2 1/7] io_uring: fix overflow resched cqe reordering Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 2/7] io_uring: init overflow entry before passing to tracing Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 3/7] io_uring: open code io_req_cqe_overflow() Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 4/7] io_uring: split __io_cqring_overflow_flush() Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 5/7] io_uring: separate lock for protecting overflow list Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 6/7] io_uring: avoid GFP_ATOMIC for overflows if possible Pavel Begunkov
2025-05-17 12:27 ` [PATCH v2 7/7] io_uring: add lockdep warning for overflow posting Pavel Begunkov
2025-05-21 13:02 ` (subset) [PATCH v2 0/7] simplify overflow CQE handling 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 \
    --in-reply-to=cover.1747483784.git.asml.silence@gmail.com \
    --to=asml.silence@gmail.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