From: yangerkun <yangerkun@huawei.com>
To: Jackie Liu <liuyun01@kylinos.cn>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>
Subject: Re: [PATCH 1/2] io_uring: make the logic clearer for io_sequence_defer
Date: Fri, 11 Oct 2019 10:24:47 +0800 [thread overview]
Message-ID: <7af32ce6-dc8f-6683-2b99-95eefb598bff@huawei.com> (raw)
In-Reply-To: <20191009011959.2203-1-liuyun01@kylinos.cn>
On 2019/10/9 9:19, Jackie Liu wrote:
> __io_get_deferred_req is used to get all defer lists, including defer_list
> and timeout_list, but io_sequence_defer should be only cares about the sequence.
>
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
> ---
> fs/io_uring.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 8a0381f1a43b..8ec2443eb019 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -418,9 +418,7 @@ static struct io_ring_ctx *io_ring_ctx_alloc(struct io_uring_params *p)
> static inline bool io_sequence_defer(struct io_ring_ctx *ctx,
> struct io_kiocb *req)
> {
> - /* timeout requests always honor sequence */
> - if (!(req->flags & REQ_F_TIMEOUT) &&
> - (req->flags & (REQ_F_IO_DRAIN|REQ_F_IO_DRAINED)) != REQ_F_IO_DRAIN)
> + if ((req->flags & (REQ_F_IO_DRAIN|REQ_F_IO_DRAINED)) != REQ_F_IO_DRAIN)
> return false;
>
> return req->sequence != ctx->cached_cq_tail + ctx->rings->sq_dropped;
> @@ -435,12 +433,11 @@ static struct io_kiocb *__io_get_deferred_req(struct io_ring_ctx *ctx,
> return NULL;
>
> req = list_first_entry(list, struct io_kiocb, list);
> - if (!io_sequence_defer(ctx, req)) {
> - list_del_init(&req->list);
> - return req;
> - }
> + if (!(req->flags & REQ_F_TIMEOUT) && io_sequence_defer(ctx, req))
> + return NULL;
Hi,
For timeout req, we should also compare the sequence to determine to
return NULL or the req. But now we will return req directly. Actually,
no need to compare req->flags with REQ_F_TIMEOUT.
Another problem, before this change, a timeout req can also drain the
sqe(io_queue_sqe->io_req_defer and add to refer list), i am not sure is
it a right or wrong logic, but your patch fix that.
Thanks,
Kun.
>
> - return NULL;
> + list_del_init(&req->list);
> + return req;
> }
>
> static struct io_kiocb *io_get_deferred_req(struct io_ring_ctx *ctx)
>
next prev parent reply other threads:[~2019-10-11 2:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 1:19 [PATCH 1/2] io_uring: make the logic clearer for io_sequence_defer Jackie Liu
2019-10-09 1:19 ` [PATCH 2/2] io_uring: replace s->needs_lock with s->in_async Jackie Liu
2019-10-10 16:10 ` Jens Axboe
2019-10-10 16:10 ` [PATCH 1/2] io_uring: make the logic clearer for io_sequence_defer Jens Axboe
2019-10-11 2:24 ` yangerkun [this message]
2019-10-11 2:35 ` Jens Axboe
2019-10-11 3:06 ` Jackie Liu
2019-10-11 3:17 ` Jens Axboe
2019-10-11 3:26 ` Jens Axboe
2019-10-11 3:27 ` Jackie Liu
2019-10-11 3:34 ` Jens Axboe
2019-10-11 3:41 ` Jackie Liu
2019-10-11 3:42 ` Jens Axboe
2019-10-11 3:43 ` Jackie Liu
2019-10-11 3:47 ` 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=7af32ce6-dc8f-6683-2b99-95eefb598bff@huawei.com \
--to=yangerkun@huawei.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=liuyun01@kylinos.cn \
/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).