public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Hao_Xu <[email protected]>
Cc: [email protected]
Subject: Re: [Question] about async buffered reads feature
Date: Fri, 25 Sep 2020 15:23:16 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 9/25/20 3:18 AM, Hao_Xu wrote:
> Hi Jens,
> I'm doing tests about this feature: [PATCHSET RFC 0/11] Add support for 
> async buffered reads
> But currently with fio testing, I found the code doesn't go to the 
> essential places in the function generic_file_buffered_read:
> 
>            if (iocb->ki_flags & IOCB_WAITQ) {
>                    if (written) {
>                            put_page(page);
>                            goto out;
>                    }
>                    error = wait_on_page_locked_async(page,
>                                                    iocb->ki_waitq);
>            } else {
> 
> and
> 
>    page_not_up_to_date:
>           /* Get exclusive access to the page ... */
>           if (iocb->ki_flags & IOCB_WAITQ)
>                   error = lock_page_async(page, iocb->ki_waitq);
>           else

Can you try with this added? Looks like a regression got introduced...


diff --git a/fs/io_uring.c b/fs/io_uring.c
index 40670ad4446c..99b842ac2dc0 100644
--- a/fs/io_uring.c
+++ b/fs/io_uring.c
@@ -3339,10 +3339,7 @@ static int io_read(struct io_kiocb *req, bool force_nonblock,
 			goto done;
 		/* some cases will consume bytes even on error returns */
 		iov_iter_revert(iter, iov_count - iov_iter_count(iter));
-		ret = io_setup_async_rw(req, iovec, inline_vecs, iter, false);
-		if (ret)
-			goto out_free;
-		return -EAGAIN;
+		goto copy_iov;
 	} else if (ret < 0) {
 		/* make sure -ERESTARTSYS -> -EINTR is done */
 		goto done;

-- 
Jens Axboe


  reply	other threads:[~2020-09-25 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  9:18 [Question] about async buffered reads feature Hao_Xu
2020-09-25 21:23 ` Jens Axboe [this message]
2020-09-25 21:39   ` 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 \
    [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