From: "NeilBrown" <neilb@suse.de>
To: "Miklos Szeredi" <miklos@szeredi.hu>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Jan Kara" <jack@suse.cz>,
"Wu Fengguang" <fengguang.wu@intel.com>,
"Jaegeuk Kim" <jaegeuk@kernel.org>, "Chao Yu" <chao@kernel.org>,
"Jeff Layton" <jlayton@kernel.org>,
"Ilya Dryomov" <idryomov@gmail.com>,
"Trond Myklebust" <trond.myklebust@hammerspace.com>,
"Anna Schumaker" <anna.schumaker@netapp.com>,
"Ryusuke Konishi" <konishi.ryusuke@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
"Philipp Reisner" <philipp.reisner@linbit.com>,
"Lars Ellenberg" <lars.ellenberg@linbit.com>,
"Paolo Valente" <paolo.valente@linaro.org>,
"Jens Axboe" <axboe@kernel.dk>,
linux-doc@vger.kernel.org, "linux-mm" <linux-mm@kvack.org>,
linux-nilfs@vger.kernel.org,
"Linux NFS list" <linux-nfs@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
"Ext4" <linux-ext4@vger.kernel.org>,
ceph-devel@vger.kernel.org, drbd-dev@lists.linbit.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/11] MM: improve cleanup when ->readpages doesn't process all pages.
Date: Fri, 04 Mar 2022 13:23:14 +1100 [thread overview]
Message-ID: <164636059432.13165.6442580674358743838@noble.neil.brown.name> (raw)
In-Reply-To: <CAJfpegs=DhCO62EFV0Q_i2fmqJnziJy1t4itP9deS=FuWEA=TQ@mail.gmail.com>
On Wed, 02 Mar 2022, Miklos Szeredi wrote:
> On Tue, 22 Feb 2022 at 04:18, NeilBrown <neilb@suse.de> wrote:
> >
> > If ->readpages doesn't process all the pages, then it is best to act as
> > though they weren't requested so that a subsequent readahead can try
> > again.
> > So:
> > - remove any 'ahead' pages from the page cache so they can be loaded
> > with ->readahead() rather then multiple ->read()s
> > - update the file_ra_state to reflect the reads that were actually
> > submitted.
> >
> > This allows ->readpages() to abort early due e.g. to congestion, which
> > will then allow us to remove the inode_read_congested() test from
> > page_Cache_async_ra().
> >
> > Signed-off-by: NeilBrown <neilb@suse.de>
> > ---
> > mm/readahead.c | 19 +++++++++++++++++--
> > 1 file changed, 17 insertions(+), 2 deletions(-)
> >
> > diff --git a/mm/readahead.c b/mm/readahead.c
> > index 73b2bc5302e0..8a97bd408cf6 100644
> > --- a/mm/readahead.c
> > +++ b/mm/readahead.c
> > @@ -104,7 +104,13 @@
> > * for necessary resources (e.g. memory or indexing information) to
> > * become available. Pages in the final ``async_size`` may be
> > * considered less urgent and failure to read them is more acceptable.
> > - * They will eventually be read individually using ->readpage().
> > + * In this case it is best to use delete_from_page_cache() to remove the
> > + * pages from the page cache as is automatically done for pages that
> > + * were not fetched with readahead_page(). This will allow a
> > + * subsequent synchronous read ahead request to try them again. If they
> > + * are left in the page cache, then they will be read individually using
> > + * ->readpage().
> > + *
> > */
> >
> > #include <linux/kernel.h>
> > @@ -226,8 +232,17 @@ static void read_pages(struct readahead_control *rac, struct list_head *pages,
> >
> > if (aops->readahead) {
> > aops->readahead(rac);
> > - /* Clean up the remaining pages */
> > + /*
> > + * Clean up the remaining pages. The sizes in ->ra
> > + * maybe be used to size next read-ahead, so make sure
> > + * they accurately reflect what happened.
> > + */
> > while ((page = readahead_page(rac))) {
> > + rac->ra->size -= 1;
> > + if (rac->ra->async_size > 0) {
> > + rac->ra->async_size -= 1;
> > + delete_from_page_cache(page);
> > + }
>
> Does the above imply that filesystem should submit at least ra->size
> pages, regardless of congestion?
ra->size - ra_async_size
pages should be submitted reguardless of congestion.
NeilBrown
next prev parent reply other threads:[~2022-03-04 3:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 3:17 [PATCH 00/11] Remove remaining parts of congestion tracking code NeilBrown
2022-02-22 3:17 ` [PATCH 04/11] fuse: remove reliance on bdi congestion NeilBrown
2022-03-01 13:27 ` Miklos Szeredi
2022-03-04 2:42 ` NeilBrown
2022-02-22 3:17 ` [PATCH 08/11] Remove bdi_congested() and wb_congested() and related functions NeilBrown
2022-02-22 3:17 ` [PATCH 06/11] ceph: remove reliance on bdi congestion NeilBrown
2022-02-23 15:43 ` Jeff Layton
2022-02-24 5:41 ` NeilBrown
2022-02-24 11:30 ` Jeff Layton
2022-03-04 2:47 ` NeilBrown
2022-03-04 11:14 ` Jeff Layton
2022-02-22 3:17 ` [PATCH 09/11] f2fs: replace congestion_wait() calls with io_schedule_timeout() NeilBrown
2022-02-22 3:17 ` [PATCH 03/11] MM: improve cleanup when ->readpages doesn't process all pages NeilBrown
2022-03-01 13:00 ` Miklos Szeredi
2022-03-04 2:23 ` NeilBrown [this message]
2022-02-22 3:17 ` [PATCH 02/11] MM: document and polish read-ahead code NeilBrown
2022-02-22 3:17 ` [PATCH 05/11] nfs: remove reliance on bdi congestion NeilBrown
2022-02-22 3:17 ` [PATCH 01/11] DOC: convert 'subsection' to 'section' in gfp.h NeilBrown
2022-02-22 3:17 ` [PATCH 11/11] Remove congestion tracking framework NeilBrown
2022-02-22 3:17 ` [PATCH 10/11] block/bfq-iosched.c: use "false" rather than "BLK_RW_ASYNC" NeilBrown
2022-02-22 3:17 ` [PATCH 07/11] Remove inode_congested() NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 5:37 [PATCH 00/11] Remove remaining parts of congestion tracking code NeilBrown
2022-02-10 5:37 ` [PATCH 03/11] MM: improve cleanup when ->readpages doesn't process all pages NeilBrown
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=164636059432.13165.6442580674358743838@noble.neil.brown.name \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@netapp.com \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=drbd-dev@lists.linbit.com \
--cc=fengguang.wu@intel.com \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=konishi.ryusuke@gmail.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=paolo.valente@linaro.org \
--cc=philipp.reisner@linbit.com \
--cc=trond.myklebust@hammerspace.com \
/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