From: Chris Mason <clm@fb.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Roman Gushchin <guro@fb.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mhocko@kernel.org" <mhocko@kernel.org>,
"vdavydov.dev@gmail.com" <vdavydov.dev@gmail.com>
Subject: Re: [PATCH 1/2] Revert "mm: don't reclaim inodes with many attached pages"
Date: Wed, 30 Jan 2019 12:21:07 +0000 [thread overview]
Message-ID: <25EAF93D-BC63-4409-AF21-F45B2DDF5D66@fb.com> (raw)
In-Reply-To: <20190130041707.27750-2-david@fromorbit.com>
On 29 Jan 2019, at 23:17, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> This reverts commit a76cf1a474d7dbcd9336b5f5afb0162baa142cf0.
>
> This change causes serious changes to page cache and inode cache
> behaviour and balance, resulting in major performance regressions
> when combining worklaods such as large file copies and kernel
> compiles.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=202441
I'm a little confused by the latest comment in the bz:
https://bugzilla.kernel.org/show_bug.cgi?id=202441#c24
Are these reverts sufficient?
Roman beat me to suggesting Rik's followup. We hit a different problem
in prod with small slabs, and have a lot of instrumentation on Rik's
code helping.
-chris
next prev parent reply other threads:[~2019-01-30 12:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 4:17 [PATCH 0/2] [REGRESSION v4.19-20] mm: shrinkers are now way too aggressive Dave Chinner
2019-01-30 4:17 ` [PATCH 1/2] Revert "mm: don't reclaim inodes with many attached pages" Dave Chinner
2019-01-30 12:21 ` Chris Mason [this message]
2019-01-31 1:34 ` Dave Chinner
2019-01-31 9:10 ` Michal Hocko
2019-01-31 18:57 ` Roman Gushchin
2019-01-31 22:19 ` Dave Chinner
2019-02-04 21:47 ` Dave Chinner
2019-02-07 10:27 ` Jan Kara
2019-02-08 5:37 ` Andrew Morton
2019-02-08 9:55 ` Jan Kara
2019-02-08 12:50 ` Jan Kara
2019-02-08 22:49 ` Andrew Morton
2019-02-09 3:42 ` Roman Gushchin
2019-02-08 21:25 ` Dave Chinner
2019-02-11 15:34 ` Wolfgang Walter
2019-01-31 15:48 ` Chris Mason
2019-02-01 23:39 ` Dave Chinner
2019-01-30 4:17 ` [PATCH 2/2] Revert "mm: slowly shrink slabs with a relatively small number of objects" Dave Chinner
2019-01-30 5:48 ` [PATCH 0/2] [REGRESSION v4.19-20] mm: shrinkers are now way too aggressive Roman Gushchin
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=25EAF93D-BC63-4409-AF21-F45B2DDF5D66@fb.com \
--to=clm@fb.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=guro@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=vdavydov.dev@gmail.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).