linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Wei Wang <wvw@google.com>
Cc: gregkh@linuxfoundation.org, "Todd Poynor" <toddpoynor@google.com>,
	"Wei Wang" <wei.vince.wang@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Michal Hocko" <mhocko@suse.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	"Jan Kara" <jack@suse.cz>, "Jérôme Glisse" <jglisse@redhat.com>,
	"Hugh Dickins" <hughd@google.com>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Sherry Cheung" <SCheung@nvidia.com>,
	"Oliver O'Halloran" <oohall@gmail.com>,
	"Andrey Ryabinin" <aryabinin@virtuozzo.com>,
	"Huang Ying" <ying.huang@intel.com>,
	"Dennis Zhou" <dennisz@fb.com>,
	"Pavel Tatashin" <pasha.tatashin@oracle.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	mgorman@suse.de
Subject: Re: [PATCH] mm: add config for readahead window
Date: Tue, 20 Mar 2018 21:17:30 +0100	[thread overview]
Message-ID: <20180320201730.xvvpc4gptqrn47ba@quack2.suse.cz> (raw)
In-Reply-To: <CAGXk5yoVMd9B=nvob7s=niCAQ9oHAX84eupF9Eet_dAk7WTStg@mail.gmail.com>

On Fri 16-03-18 18:49:08, Wei Wang wrote:
> Android devices boot time benefits by bigger readahead window setting from
> init. This patch will make readahead window a config so early boot can benefit
> by it as well.
> 
> 
> On Fri, Mar 16, 2018 at 11:25 AM Wei Wang <wvw@google.com> wrote:
> 
>     From: Wei Wang <wvw@google.com>
> 
>     Change VM_MAX_READAHEAD value from the default 128KB to a configurable
>     value. This will allow the readahead window to grow to a maximum size
>     bigger than 128KB during boot, which could benefit to sequential read
>     throughput and thus boot performance.
> 
>     Signed-off-by: Wei Wang <wvw@google.com>

Just for record we had VM_MAX_READAHEAD changed to 512 in all SUSE
distributions for quite some years. But just recently we were re-evaluating
it and we are finding less and less reasons to keep this setting to 512 -
with newer storage benefits become marginal and the overhead of reading
more unnecessarily in some other corner cases is visible as well (I still
have somewhere reports from 0-day robot that complained to me about two
performance regressions coming from increased default readahead window).

So for your specific case it might make sense to increase the window when
you have a control of both the HW and the kernel but in general I tend to
currently agree with Linus & co. that the current default is probably fine.

I don't have a strong opinion on whether your ~90ms of boot time are good
enough justification for a kernel config option...

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

  parent reply	other threads:[~2018-03-20 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 18:25 [PATCH] mm: add config for readahead window Wei Wang
2018-03-16 18:49 ` Wei Wang
2018-03-16 20:53   ` Greg KH
2018-03-19  2:36   ` Huang, Ying
2018-03-19  3:15     ` Wei Wang
2018-03-20 20:17   ` Jan Kara [this message]
2018-03-16 20:56 ` Kirill A. Shutemov
2018-03-16 21:26   ` Linus Torvalds
2018-03-16 21:33 ` Andrew Morton
2018-03-16 21:51   ` Wei Wang
2018-03-16 21:59     ` Andrew Morton
2018-03-16 22:13       ` Wei Wang

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=20180320201730.xvvpc4gptqrn47ba@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=SCheung@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=dan.j.williams@intel.com \
    --cc=dennisz@fb.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hughd@google.com \
    --cc=jglisse@redhat.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=oohall@gmail.com \
    --cc=pasha.tatashin@oracle.com \
    --cc=toddpoynor@google.com \
    --cc=wei.vince.wang@gmail.com \
    --cc=willy@infradead.org \
    --cc=wvw@google.com \
    --cc=ying.huang@intel.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).