From: Hao Xu <[email protected]>
To: Noah Goldstein <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH v1] fs/io_uring: Hoist ret2 == -EAGAIN check in tail of io_write
Date: Mon, 18 Oct 2021 20:17:57 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
在 2021/10/18 下午3:02, Noah Goldstein 写道:
> This commit reorganizes the branches in the tail of io_write so that
> the 'ret2 == -EAGAIN' check is not repeated and done first.
>
> The previous version was duplicating the 'ret2 == -EAGAIN'. As well
> 'ret2 != -EAGAIN' gurantees the 'done:' path so it makes sense to
> move that check to the front before the likely more expensive branches
> which require memory derefences.
>
> Signed-off-by: Noah Goldstein <[email protected]>
> ---
> Generally I would want to rewrite this as:
> ```
> if (ret2 != -EAGAIN
> || (req->flags & REQ_F_NOWAIT)
> || (!force_nonblock && !(req->ctx->flags & IORING_SETUP_IOPOLL)))
> kiocb_done(kiocb, ret2, issue_flags);
> else {
> ...
> ```
To me, this one is clear enough and short, but I think better to:
if (ret2 != -EAGAIN || (req->flags & REQ_F_NOWAIT) ||
(!force_nonblock && !(req->ctx->flags & IORING_SETUP_IOPOLL))
if the first line doesn't exceed the line limit.
Reviewed-by: Hao Xu <[email protected]>
>
> But the style of the file seems to be to use gotos. If the above is
> prefereable, let me know and I'll post a new version.
> fs/io_uring.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index d1e672e7a2d1..932fc84d70d3 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -3648,12 +3648,15 @@ static int io_write(struct io_kiocb *req, unsigned int issue_flags)
> */
> if (ret2 == -EOPNOTSUPP && (kiocb->ki_flags & IOCB_NOWAIT))
> ret2 = -EAGAIN;
> +
> + if (ret2 != -EAGAIN)
> + goto done;
> /* no retry on NONBLOCK nor RWF_NOWAIT */
> - if (ret2 == -EAGAIN && (req->flags & REQ_F_NOWAIT))
> + if (req->flags & REQ_F_NOWAIT)
> goto done;
> - if (!force_nonblock || ret2 != -EAGAIN) {
> + if (!force_nonblock) {
> /* IOPOLL retry should happen for io-wq threads */
> - if (ret2 == -EAGAIN && (req->ctx->flags & IORING_SETUP_IOPOLL))
> + if (req->ctx->flags & IORING_SETUP_IOPOLL)
> goto copy_iov;
> done:
> kiocb_done(kiocb, ret2, issue_flags);
>
next prev parent reply other threads:[~2021-10-18 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 7:02 [PATCH v1] fs/io_uring: Hoist ret2 == -EAGAIN check in tail of io_write Noah Goldstein
2021-10-18 12:17 ` Hao Xu [this message]
2021-10-18 14:56 ` [PATCH v2] " Noah Goldstein
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=f27e1842-f22e-a40d-7055-6f924b13100f@linux.alibaba.com \
[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