From: Matthew Wilcox <[email protected]>
To: Hao Xu <[email protected]>
Cc: Jens Axboe <[email protected]>,
[email protected], [email protected],
Johannes Weiner <[email protected]>,
Andrew Morton <[email protected]>
Subject: Re: [PATCH RFC] mm: fix the sync buffered read to the old way
Date: Thu, 22 Oct 2020 15:10:37 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, Oct 22, 2020 at 09:58:34PM +0800, Hao Xu wrote:
> The commit 324bcf54c449 changed the code path of async buffered reads
> to go with the page_cache_sync_readahead() way when readahead is
> disabled, meanwhile the sync buffered reads are forced to do IO in the
> above way as well, which makes it go to a more complex code path.
But ->readpage is (increasingly) synchronous while readahead should be
used to start async I/Os. I'm pretty sure Jens meant to do exactly what
he did.
next prev parent reply other threads:[~2020-10-22 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 13:58 [PATCH RFC] mm: fix the sync buffered read to the old way Hao Xu
2020-10-22 14:10 ` Matthew Wilcox [this message]
2020-10-22 14:55 ` Hao_Xu
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] \
[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