From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: optimise kiocb_set_rw_flags()
Date: Sat, 1 Aug 2020 13:42:39 +0300 [thread overview]
Message-ID: <d79b17cd-2a48-3802-87a5-030ff6d64a53@gmail.com> (raw)
In-Reply-To: <e523f51f59ad6ecdad4ad22c560cb9c913e96e1a.1596277420.git.asml.silence@gmail.com>
On 01/08/2020 13:36, Pavel Begunkov wrote:
> Use a local var to collect flags in kiocb_set_rw_flags(). That spares
> some memory writes and allows to replace most of the jumps with MOVEcc.
This one is pretty old, but looks like nobody in fsdevel cares.
Jens, any chance you can pick this up? For instancec, I don't like the
binary it generates for io_uring.
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
> ---
>
> v2: fast exit on flags == 0 (Matthew Wilcox)
>
> include/linux/fs.h | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 8a00ba99284e..b7f1f1b7d691 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -3282,22 +3282,28 @@ static inline int iocb_flags(struct file *file)
>
> static inline int kiocb_set_rw_flags(struct kiocb *ki, rwf_t flags)
> {
> + int kiocb_flags = 0;
> +
> + if (!flags)
> + return 0;
> if (unlikely(flags & ~RWF_SUPPORTED))
> return -EOPNOTSUPP;
>
> if (flags & RWF_NOWAIT) {
> if (!(ki->ki_filp->f_mode & FMODE_NOWAIT))
> return -EOPNOTSUPP;
> - ki->ki_flags |= IOCB_NOWAIT;
> + kiocb_flags |= IOCB_NOWAIT;
> }
> if (flags & RWF_HIPRI)
> - ki->ki_flags |= IOCB_HIPRI;
> + kiocb_flags |= IOCB_HIPRI;
> if (flags & RWF_DSYNC)
> - ki->ki_flags |= IOCB_DSYNC;
> + kiocb_flags |= IOCB_DSYNC;
> if (flags & RWF_SYNC)
> - ki->ki_flags |= (IOCB_DSYNC | IOCB_SYNC);
> + kiocb_flags |= (IOCB_DSYNC | IOCB_SYNC);
> if (flags & RWF_APPEND)
> - ki->ki_flags |= IOCB_APPEND;
> + kiocb_flags |= IOCB_APPEND;
> +
> + ki->ki_flags |= kiocb_flags;
> return 0;
> }
>
>
--
Pavel Begunkov
next prev parent reply other threads:[~2020-08-01 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 10:36 [PATCH] fs: optimise kiocb_set_rw_flags() Pavel Begunkov
2020-08-01 10:42 ` Pavel Begunkov [this message]
2020-08-01 15:37 ` Matthew Wilcox
2020-08-01 17:01 ` Jens Axboe
2020-08-02 8:33 ` Pavel Begunkov
2020-08-02 8:41 ` Pavel Begunkov
2020-08-01 17:02 ` Jens Axboe
2020-08-02 8:21 ` Pavel Begunkov
-- strict thread matches above, loose matches on Subject: below --
2020-01-17 1:16 Pavel Begunkov
2020-01-17 1:21 ` Matthew Wilcox
2020-01-17 1:23 ` 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=d79b17cd-2a48-3802-87a5-030ff6d64a53@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).