From: Dave Chinner <dchinner@redhat.com>
To: Roman Gushchin <guro@fb.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"dairinin@gmail.com" <dairinin@gmail.com>,
"mhocko@kernel.org" <mhocko@kernel.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"riel@surriel.com" <riel@surriel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: + revert-mm-dont-reclaim-inodes-with-many-attached-pages.patch added to -mm tree
Date: Thu, 31 Jan 2019 12:44:35 +1100 [thread overview]
Message-ID: <20190131014435.GM31397@rh> (raw)
In-Reply-To: <20190130055420.GB2107@castle.DHCP.thefacebook.com>
On Wed, Jan 30, 2019 at 05:54:27AM +0000, Roman Gushchin wrote:
> Hi, Andrew!
>
> I believe, that Rik's patch ( https://lkml.org/lkml/2019/1/28/1865 ) can make
> a difference here, and might fix the regression. I'd give it a chance, before
> reverting these two patches. Reverting will re-introduce the memcg-leak, which
> is quite bad.
Rik's change is just another hack that will still have effects on
reclaim behaviour.
Indeed, the fs/inode.c change definitely needs reverting, because
that is just *plain wrong* and breaks long-standing memory reclaim
behaviour.
I seriously disagree with shovelling a different, largely untested
and contentious change to the shrinker algorithm to try and patch
over the symptoms of the original change. It leaves the underlying
problem unfixed (dying memcgs need a reaper to shrink the remaining
slab objects that pin that specific memcg) and instead plays
"whack-a-mole" on what we alreayd know is a fundamentally broken
assumption (i.e. that shrinking small slabs more agressively is
side-effect free).
-Dave.
--
Dave Chinner
dchinner@redhat.com
next prev parent reply other threads:[~2019-01-31 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 5:10 + revert-mm-dont-reclaim-inodes-with-many-attached-pages.patch added to -mm tree akpm
2019-01-30 5:54 ` Roman Gushchin
2019-01-30 22:10 ` Andrew Morton
2019-01-31 1:44 ` Dave Chinner [this message]
2019-01-31 2:33 ` Rik van Riel
2019-01-31 22:49 ` Dave Chinner
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=20190131014435.GM31397@rh \
--to=dchinner@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dairinin@gmail.com \
--cc=guro@fb.com \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.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