From: Hao_Xu <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [Question] about async buffered reads feature
Date: Fri, 25 Sep 2020 17:18:52 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
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
could you give me a copy of your test program which you mentioned in the
RFC?
My testing environment:
fio version: 3.10
kernel version: the mainline kernel, latest commit is
805c6d3c19210c90c109107d189744e960eae025
Thanks,
Hao
next reply other threads:[~2020-09-25 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:18 Hao_Xu [this message]
2020-09-25 21:23 ` [Question] about async buffered reads feature Jens Axboe
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 \
--in-reply-to=a1bd6dfd-c911-dfe8-ec7f-4fac5ac8c73e@linux.alibaba.com \
[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