public inbox for [email protected]
 help / color / mirror / Atom feed
From: Dylan Yudaken <[email protected]>
To: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Cc: <[email protected]>, <[email protected]>,
	Dylan Yudaken <[email protected]>
Subject: [PATCH for-next 0/4] io_uring: cleanup allow_overflow on post_cqe
Date: Mon, 7 Nov 2022 04:52:32 -0800	[thread overview]
Message-ID: <[email protected]> (raw)

Previously, CQE ordering could be broken in multishot if there was an
overflow, and so the multishot was stopped in overflow. However since
Pavel's change in commit aa1df3a360a0 ("io_uring: fix CQE reordering"),
there is no risk of out of order completions being received by userspace.

So we can now clean up this code.

Dylan Yudaken (4):
  io_uring: revert "io_uring fix multishot accept ordering"
  io_uring: revert "io_uring: fix multishot poll on overflow"
  io_uring: allow multishot recv CQEs to overflow
  io_uring: remove allow_overflow parameter

 io_uring/io_uring.c | 13 ++++---------
 io_uring/io_uring.h |  6 ++----
 io_uring/msg_ring.c |  4 ++--
 io_uring/net.c      | 19 ++++++-------------
 io_uring/poll.c     |  6 ++----
 io_uring/rsrc.c     |  4 ++--
 6 files changed, 18 insertions(+), 34 deletions(-)


base-commit: 765d0e263fccc8b22efef8258c3260e9d0ecf632
-- 
2.30.2


             reply	other threads:[~2022-11-07 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 12:52 Dylan Yudaken [this message]
2022-11-07 12:52 ` [PATCH for-next 1/4] io_uring: revert "io_uring fix multishot accept ordering" Dylan Yudaken
2022-11-07 12:52 ` [PATCH for-next 2/4] io_uring: revert "io_uring: fix multishot poll on overflow" Dylan Yudaken
2022-11-07 12:52 ` [PATCH for-next 3/4] io_uring: allow multishot recv CQEs to overflow Dylan Yudaken
2022-11-07 12:52 ` [PATCH for-next 4/4] io_uring: remove allow_overflow parameter Dylan Yudaken
2022-11-07 20:18 ` [PATCH for-next 0/4] io_uring: cleanup allow_overflow on post_cqe 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] \
    [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