From: Hugh Dickins <hughd@google.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Song Liu <songliubraving@fb.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm,thp: stop leaking unreleased file pages
Date: Wed, 3 Jun 2020 15:19:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.2006031506500.32284@eggly.anvils> (raw)
In-Reply-To: <20200603215122.GR19604@bombadil.infradead.org>
On Wed, 3 Jun 2020, Matthew Wilcox wrote:
> On Wed, May 27, 2020 at 02:28:10PM -0700, Hugh Dickins wrote:
> > Saying "source inspection" reminds me: there is another funny in there,
> > but I don't think it matters very much in practice, and might need
> > rather a lot of testing to justify any particular patch: where
> > page_cache_sync_readahead() asks for PAGE_SIZE pages!
> >
> > "end - index" seems a more reasonable number to me: but then we
> > might find that reading ahead into the next huge extent had actually
> > been a useful optimization (and those readahead functions impose
> > their own caps, so PAGE_SIZE shouldn't work out too outrageously).
>
> That readahead was only added in 99cb0dbd47a15d395bf3faa78dc122bc5efe3fc0
> so it probably hasn't really been performance tested yet.
I can well imagine that an entirely new body of code, exercised
in the background by khugepaged, will not be a leading candidate for
performance comparisons - rightly so; but arguing that by the commit
being in the tree for only eight months seems... odd :)
Hugh
prev parent reply other threads:[~2020-06-03 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 1:50 Hugh Dickins
2020-05-25 0:05 ` Song Liu
2020-05-25 4:32 ` Kirill A. Shutemov
2020-05-26 16:01 ` Johannes Weiner
2020-05-27 21:28 ` Hugh Dickins
2020-05-28 8:51 ` Naresh Kamboju
2020-06-03 21:51 ` Matthew Wilcox
2020-06-03 22:19 ` Hugh Dickins [this message]
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=alpine.LSU.2.11.2006031506500.32284@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songliubraving@fb.com \
--cc=willy@infradead.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