From: Stefano Garzarella <[email protected]>
To: Xiaoguang Wang <[email protected]>
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCH] io_uring: cleanup io_alloc_async_ctx()
Date: Fri, 27 Mar 2020 09:26:24 +0100 [thread overview]
Message-ID: <20200327082624.wrugiip4jkkvmw2s@steredhat> (raw)
In-Reply-To: <[email protected]>
On Fri, Mar 27, 2020 at 03:36:52PM +0800, Xiaoguang Wang wrote:
> Cleanup io_alloc_async_ctx() a bit, add a new __io_alloc_async_ctx(),
> so io_setup_async_rw() won't need to check whether async_ctx is true
> or false again.
>
> Signed-off-by: Xiaoguang Wang <[email protected]>
> ---
> fs/io_uring.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
Looks good to me!
Reviewed-by: Stefano Garzarella <[email protected]>
Thanks,
Stefano
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 3affd96a98ba..a85659eae137 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -2169,12 +2169,18 @@ static void io_req_map_rw(struct io_kiocb *req, ssize_t io_size,
> }
> }
>
> +static inline int __io_alloc_async_ctx(struct io_kiocb *req)
> +{
> + req->io = kmalloc(sizeof(*req->io), GFP_KERNEL);
> + return req->io == NULL;
> +}
> +
> static int io_alloc_async_ctx(struct io_kiocb *req)
> {
> if (!io_op_defs[req->opcode].async_ctx)
> return 0;
> - req->io = kmalloc(sizeof(*req->io), GFP_KERNEL);
> - return req->io == NULL;
> +
> + return __io_alloc_async_ctx(req);
> }
>
> static int io_setup_async_rw(struct io_kiocb *req, ssize_t io_size,
> @@ -2184,7 +2190,7 @@ static int io_setup_async_rw(struct io_kiocb *req, ssize_t io_size,
> if (!io_op_defs[req->opcode].async_ctx)
> return 0;
> if (!req->io) {
> - if (io_alloc_async_ctx(req))
> + if (__io_alloc_async_ctx(req))
> return -ENOMEM;
>
> io_req_map_rw(req, io_size, iovec, fast_iov, iter);
> --
> 2.17.2
>
next prev parent reply other threads:[~2020-03-27 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 7:36 [PATCH] io_uring: cleanup io_alloc_async_ctx() Xiaoguang Wang
2020-03-27 8:26 ` Stefano Garzarella [this message]
2020-03-27 14:54 ` 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=20200327082624.wrugiip4jkkvmw2s@steredhat \
[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