From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, asml.silence@gmail.com
Subject: [PATCH for-next 0/6] clean up __io_fill_cqe_req()
Date: Fri, 17 Jun 2022 09:47:59 +0100 [thread overview]
Message-ID: <cover.1655455613.git.asml.silence@gmail.com> (raw)
Clean up __io_fill_cqe_req() after recent changes
Pavel Begunkov (6):
io_uring: don't expose io_fill_cqe_aux()
io_uring: don't inline __io_get_cqe()
io_uring: introduce io_req_cqe_overflow()
io_uring: deduplicate __io_fill_cqe_req tracing
io_uring: deduplicate io_get_cqe() calls
io_uring: change ->cqe_cached invariant for CQE32
io_uring/io_uring.c | 73 +++++++++++++++++++++++++++++--
io_uring/io_uring.h | 104 ++++++++++----------------------------------
io_uring/msg_ring.c | 11 +----
io_uring/net.c | 20 +++------
io_uring/poll.c | 24 ++++------
io_uring/rsrc.c | 14 +++---
6 files changed, 110 insertions(+), 136 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-17 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:47 Pavel Begunkov [this message]
2022-06-17 8:48 ` [PATCH for-next 1/6] io_uring: don't expose io_fill_cqe_aux() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 2/6] io_uring: don't inline __io_get_cqe() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 3/6] io_uring: introduce io_req_cqe_overflow() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 4/6] io_uring: deduplicate __io_fill_cqe_req tracing Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 5/6] io_uring: deduplicate io_get_cqe() calls Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 6/6] io_uring: change ->cqe_cached invariant for CQE32 Pavel Begunkov
2022-06-17 13:35 ` [PATCH for-next 0/6] clean up __io_fill_cqe_req() 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.1655455613.git.asml.silence@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.