From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH 2/3] io_uring: put flag checking for needing req cleanup in one spot
Date: Fri, 16 Apr 2021 14:25:43 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 16/04/2021 02:25, Jens Axboe wrote:
> We have this in two spots right now, which is a bit fragile. In
> preparation for moving REQ_F_POLLED cleanup into the same spot, move
> the check into io_clean_op() itself so we only have it once.
>
> Signed-off-by: Jens Axboe <[email protected]>
> ---
> fs/io_uring.c | 19 ++++++++-----------
> 1 file changed, 8 insertions(+), 11 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 87ce3dbcd4ca..a668d6a3319c 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -1601,8 +1601,7 @@ static void io_req_complete_post(struct io_kiocb *req, long res,
> static void io_req_complete_state(struct io_kiocb *req, long res,
> unsigned int cflags)
> {
> - if (req->flags & (REQ_F_NEED_CLEANUP | REQ_F_BUFFER_SELECTED))
> - io_clean_op(req);
> + io_clean_op(req);
> req->result = res;
> req->compl.cflags = cflags;
> req->flags |= REQ_F_COMPLETE_INLINE;
> @@ -1713,16 +1712,12 @@ static void io_dismantle_req(struct io_kiocb *req)
>
> if (!(flags & REQ_F_FIXED_FILE))
> io_put_file(req->file);
> - if (flags & (REQ_F_NEED_CLEANUP | REQ_F_BUFFER_SELECTED |
> - REQ_F_INFLIGHT)) {
> - io_clean_op(req);
> + io_clean_op(req);
> + if (req->flags & REQ_F_INFLIGHT) {
> + struct io_uring_task *tctx = req->task->io_uring;
Not in particular happy about it.
1. adds extra if
2. adds extra function call
3. extra memory load in that function call.
Pushes us back in terms of performance. I'd suggest to have
a helper, which is pretty much optimisable and may be coalesced by a compiler with
adjacent flag checks.
static inline bool io_need_cleanup(unsigned flags)
{
return flags & (REQ_F_NEED_CLEANUP | REQ_F_BUFFER_SELECTED);
}
if (io_need_cleanup(flags) || (flags & INFLIGHT)) {
io_clean_op();
if (INFLIGHT) {}
}
>
> - if (req->flags & REQ_F_INFLIGHT) {
> - struct io_uring_task *tctx = req->task->io_uring;
> -
> - atomic_dec(&tctx->inflight_tracked);
> - req->flags &= ~REQ_F_INFLIGHT;
> - }
> + atomic_dec(&tctx->inflight_tracked);
> + req->flags &= ~REQ_F_INFLIGHT;
> }
> if (req->fixed_rsrc_refs)
> percpu_ref_put(req->fixed_rsrc_refs);
> @@ -5995,6 +5990,8 @@ static int io_req_defer(struct io_kiocb *req)
>
> static void io_clean_op(struct io_kiocb *req)
> {
> + if (!(req->flags & (REQ_F_BUFFER_SELECTED | REQ_F_NEED_CLEANUP)))
> + return;
> if (req->flags & REQ_F_BUFFER_SELECTED) {
> switch (req->opcode) {
> case IORING_OP_READV:
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-04-16 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 1:25 [PATCH 0/3] Misc 5.13 fixes Jens Axboe
2021-04-16 1:25 ` [PATCH 1/3] io_uring: disable multishot poll for double poll add cases Jens Axboe
2021-04-16 1:25 ` [PATCH 2/3] io_uring: put flag checking for needing req cleanup in one spot Jens Axboe
2021-04-16 13:25 ` Pavel Begunkov [this message]
2021-04-16 15:42 ` Jens Axboe
2021-04-16 1:25 ` [PATCH 3/3] io_uring: tie req->apoll to request lifetime Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-04-16 16:10 [PATCH v2 0/3] Misc 5.13 fixes Jens Axboe
2021-04-16 16:10 ` [PATCH 2/3] io_uring: put flag checking for needing req cleanup in one spot Jens Axboe
2021-04-16 23:37 ` 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 \
[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