On Wed, May 22, 2019 at 02:59:06PM -0700, Andrew Morton wrote:
> On Wed, 22 May 2019 21:43:54 +0000 Roman Gushchin <guro@xxxxxx> wrote:
>
> > Is this patchset good to go? Or do you have any remaining concerns?
> >
> > It has been carefully reviewed by Shakeel; and also Christoph and Waiman
> > gave some attention to it.
> >
> > Since commit 172b06c32b94 ("mm: slowly shrink slabs with a relatively")
> > has been reverted, the memcg "leak" problem is open again, and I've heard
> > from several independent people and companies that it's a real problem
> > for them. So it will be nice to close it asap.
> >
> > I suspect that the fix is too heavy for stable, unfortunately.
> >
> > Please, let me know if you have any issues that preventing you
> > from pulling it into the tree.
>
> I looked, and put it on ice for a while, hoping to hear from
> mhocko/hannes. Did they look at the earlier versions?
Johannes has definitely looked at one of early versions of the patchset,
and one of the outcomes was his own patchset about pushing memcg stats
up by the tree, which eliminated the need to deal with memcg stats
on kmem_cache reparenting.
The problem and the proposed solution have been discussed on latest LSFMM,
and I didn't hear any opposition. So I assume that Michal is at least
not against the idea in general. A careful code review is always welcome,
of course.
Thanks!
