From: Zhaoyang Huang <huangzhaoyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Roman Gushchin <klamm@yandex-team.ru>,
Zhaoyang Huang <zhaoyang.huang@unisoc.com>,
"open list:MEMORY MANAGEMENT" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm : sync ra->ra_pages with bdi->ra_pages
Date: Mon, 17 Aug 2020 18:59:27 +0800 [thread overview]
Message-ID: <CAGWkznFYaMLUf3cazP9x9eA-SYTu6GkXR=m3q20WowGsCZLWHw@mail.gmail.com> (raw)
In-Reply-To: <20200814211459.65f6db0211872e30684a630a@linux-foundation.org>
On Sat, Aug 15, 2020 at 12:15 PM Andrew Morton
<akpm@linux-foundation.org> wrote:
>
> On Fri, 14 Aug 2020 13:10:34 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Fri, 14 Aug 2020 17:03:44 +0800 Zhaoyang Huang <huangzhaoyang@gmail.com> wrote:
> >
> > > Some system(like android) will turbo read during startup via expanding the
> > > readahead window and then set it back to normal(128kb as usual). However, some
> > > files in the system process context will keep to be opened since it is opened
> > > up and has no chance to sync with the updated value as it is almost impossible
> > > to change the files attached to the inode(processes are unaware of these things)
> >
> > How about making VM_READAHEAD_PAGES a variable?
>
> Or make it settable in Kconfig?
I don't think so. The scenario I gave before is a dynamic process,
can't be solved via menuconfig thing.
next prev parent reply other threads:[~2020-08-17 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 9:03 [PATCH] mm : sync ra->ra_pages with bdi->ra_pages Zhaoyang Huang
2020-08-14 11:48 ` Matthew Wilcox
2020-08-14 20:10 ` Andrew Morton
2020-08-15 4:14 ` Andrew Morton
2020-08-17 10:59 ` Zhaoyang Huang [this message]
2020-08-19 6:54 ` Zhaoyang Huang
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='CAGWkznFYaMLUf3cazP9x9eA-SYTu6GkXR=m3q20WowGsCZLWHw@mail.gmail.com' \
--to=huangzhaoyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=klamm@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zhaoyang.huang@unisoc.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;
as well as URLs for NNTP newsgroup(s).