From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: [PATCH 0/3] __io_queue_sqe() cleanups
Date: Thu, 22 Oct 2020 16:47:15 +0100 [thread overview]
Message-ID: <cover.1603381526.git.asml.silence@gmail.com> (raw)
Refactor __io_queue_sqe(). Easier to read, hopefully better optimisable.
Pavel Begunkov (3):
io_uring: don't miss setting IO_WQ_WORK_CONCURRENT
io_uring: simplify nxt propagation in io_queue_sqe
io_uring: simplify __io_queue_sqe()
fs/io_uring.c | 42 ++++++++++++++----------------------------
1 file changed, 14 insertions(+), 28 deletions(-)
--
2.24.0
next reply other threads:[~2020-10-22 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 15:47 Pavel Begunkov [this message]
2020-10-22 15:47 ` [PATCH 1/3] io_uring: don't miss setting IO_WQ_WORK_CONCURRENT Pavel Begunkov
2020-10-22 15:47 ` [PATCH 2/3] io_uring: simplify nxt propagation in io_queue_sqe Pavel Begunkov
2020-10-22 15:47 ` [PATCH 3/3] io_uring: simplify __io_queue_sqe() Pavel Begunkov
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.1603381526.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 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 NNTP newsgroup(s).