IO-Uring Archive mirror
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
	asml.silence@gmail.com, Ming Lei <ming.lei@redhat.com>
Subject: [PATCH for-next 0/4] clean up io_req_complete_post
Date: Fri,  5 Apr 2024 16:50:01 +0100	[thread overview]
Message-ID: <cover.1712331455.git.asml.silence@gmail.com> (raw)

Patch 1 from Ming Lei removes a good chunk of unreachable code. Add a
warning in patch 2, and apparently we can develop on the idea and remove
even more dead code in patches 3,4.

Ming Lei (1):
  io_uring: kill dead code in io_req_complete_post

Pavel Begunkov (3):
  io_uring: turn implicit assumptions into a warning
  io_uring: remove async request cache
  io_uring: remove io_req_put_rsrc_locked()

 include/linux/io_uring_types.h |  4 --
 io_uring/io_uring.c            | 72 ++++++----------------------------
 io_uring/refs.h                |  7 ++++
 io_uring/rsrc.h                |  6 ---
 4 files changed, 20 insertions(+), 69 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-04-05 15:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 15:50 Pavel Begunkov [this message]
2024-04-05 15:50 ` [PATCH for-next 1/4] io_uring: kill dead code in io_req_complete_post Pavel Begunkov
2024-04-05 15:50 ` [PATCH for-next 2/4] io_uring: turn implicit assumptions into a warning Pavel Begunkov
2024-04-06 13:21   ` Ming Lei
2024-04-05 15:50 ` [PATCH for-next 3/4] io_uring: remove async request cache Pavel Begunkov
2024-04-06 13:26   ` Ming Lei
2024-04-05 15:50 ` [PATCH for-next 4/4] io_uring: remove io_req_put_rsrc_locked() Pavel Begunkov
2024-04-06 13:28   ` Ming Lei
2024-04-06  2:06 ` [PATCH for-next 0/4] clean up io_req_complete_post 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.1712331455.git.asml.silence@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).