From: Roman Gushchin <guro@fb.com>
To: Rik van Riel <riel@surriel.com>
Cc: Dave Chinner <david@fromorbit.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"dchinner@redhat.com" <dchinner@redhat.com>,
"guroan@gmail.com" <guroan@gmail.com>,
Kernel Team <Kernel-team@fb.com>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>
Subject: Re: [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues
Date: Fri, 22 Feb 2019 01:57:52 +0000 [thread overview]
Message-ID: <20190222015745.GA7582@castle.DHCP.thefacebook.com> (raw)
In-Reply-To: <2d4e6dd7a546640c9ecb6a60b730d6c3a3da980b.camel@surriel.com>
On Thu, Feb 21, 2019 at 08:48:27PM -0500, Rik van Riel wrote:
> On Thu, 2019-02-21 at 17:46 -0500, Roman Gushchin wrote:
> > On Wed, Feb 20, 2019 at 06:27:07PM +1100, Dave Chinner wrote:
> > > On Wed, Feb 20, 2019 at 04:50:31PM +1100, Dave Chinner wrote:
> > > > I'm just going to fix the original regression in the shrinker
> > > > algorithm by restoring the gradual accumulation behaviour, and
> > > > this
> > > > whole series of problems can be put to bed.
> > >
> > > Something like this lightly smoke tested patch below. It may be
> > > slightly more agressive than the original code for really small
> > > freeable values (i.e. < 100) but otherwise should be roughly
> > > equivalent to historic accumulation behaviour.
> > >
> > > Cheers,
> > >
> > > Dave.
> > > --
> > > Dave Chinner
> > > david@fromorbit.com
> > >
> > > mm: fix shrinker scan accumulation regression
> > >
> > > From: Dave Chinner <dchinner@redhat.com>
> >
> > JFYI: I'm testing this patch in our environment for fixing
> > the memcg memory leak.
> >
> > It will take a couple of days to get reliable results.
>
> Just to clarify, is this test with fls instead of ilog2,
> so the last item in a slab cache can get reclaimed as
> well?
I'm testing both version.
Thanks!
next prev parent reply other threads:[~2019-02-22 1:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 7:13 [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues Roman Gushchin
[not found] ` <20190219092323.GH4525@dhcp22.suse.cz>
2019-02-19 16:21 ` [LSF/MM ATTEND] MM track: dying memory cgroups and slab reclaim issue, memcg, THP Roman Gushchin
2019-02-20 2:47 ` [LSF/MM TOPIC] dying memory cgroups and slab reclaim issues Dave Chinner
2019-02-20 5:50 ` Dave Chinner
2019-02-20 7:27 ` Dave Chinner
2019-02-20 16:20 ` Johannes Weiner
2019-02-21 22:46 ` Roman Gushchin
2019-02-22 1:48 ` Rik van Riel
2019-02-22 1:57 ` Roman Gushchin [this message]
2019-02-28 20:30 ` Roman Gushchin
2019-02-28 21:30 ` Dave Chinner
2019-02-28 22:29 ` Roman Gushchin
-- strict thread matches above, loose matches on Subject: below --
2019-02-19 0:31 Roman Gushchin
2019-02-19 2:04 ` Dave Chinner
2019-02-19 17:31 ` Rik van Riel
2019-02-19 17:38 ` Michal Hocko
2019-02-19 23:26 ` Dave Chinner
2019-02-20 2:06 ` Rik van Riel
2019-02-20 4:33 ` Dave Chinner
2019-02-20 5:31 ` Roman Gushchin
2019-02-20 17:00 ` Rik van Riel
2019-02-18 23:53 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=20190222015745.GA7582@castle.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=Kernel-team@fb.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=guroan@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=riel@surriel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.