From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] readahead improvements
Date: Wed, 7 Apr 2021 21:18:54 +0100 [thread overview]
Message-ID: <20210407201857.3582797-1-willy@infradead.org> (raw)
As requested, fix up readahead_expand() so as to not confuse the ondemand
algorithm. Also make the documentation slightly better. Dave, could you
put in some debug and check this actually works? I don't generally test
with any filesystems that use readahead_expand(), but printing (index,
nr_to_read, lookahead_size) in page_cache_ra_unbounded() would let a human
(such as your good self) determine whether it's working approximately
as designed.
This is against linux-next 20210407.
Matthew Wilcox (Oracle) (3):
mm/filemap: Pass the file_ra_state in the ractl
fs: Document file_ra_state
mm/readahead: Adjust file_ra in readahead_expand
fs/ext4/verity.c | 2 +-
fs/f2fs/file.c | 2 +-
fs/f2fs/verity.c | 2 +-
include/linux/fs.h | 24 ++++++++++++++----------
include/linux/pagemap.h | 20 +++++++++++---------
mm/filemap.c | 4 ++--
mm/internal.h | 7 +++----
mm/readahead.c | 25 ++++++++++++++-----------
8 files changed, 47 insertions(+), 39 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-07 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 20:18 Matthew Wilcox (Oracle) [this message]
2021-04-07 20:18 ` [PATCH 1/3] mm/filemap: Pass the file_ra_state in the ractl Matthew Wilcox (Oracle)
2021-04-07 20:18 ` [PATCH 2/3] fs: Document file_ra_state Matthew Wilcox (Oracle)
2021-04-07 20:18 ` [PATCH 3/3] mm/readahead: Adjust file_ra in readahead_expand Matthew Wilcox (Oracle)
2021-04-07 22:43 ` [PATCH 0/3] readahead improvements David Howells
2021-04-08 10:57 ` riteshh
2021-04-08 13:15 ` Brendan Gregg
2021-04-08 12:51 ` [PATCH] mm, netfs: Fix readahead bits David Howells
2021-04-08 13:09 ` Matthew Wilcox
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=20210407201857.3582797-1-willy@infradead.org \
--to=willy@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).