From: Roman Gushchin <guro@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dennis Zhou <dennis@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Shakeel Butt <shakeelb@google.com>, <linux-mm@kvack.org>,
<kernel-team@fb.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Potential Spoof] [PATCH v2 0/5] mm: memcg accounting of percpu memory
Date: Wed, 17 Jun 2020 13:47:05 -0700 [thread overview]
Message-ID: <20200617204705.GA24694@carbon.DHCP.thefacebook.com> (raw)
In-Reply-To: <20200617133949.148aff08300e24a084f9bb18@linux-foundation.org>
On Wed, Jun 17, 2020 at 01:39:49PM -0700, Andrew Morton wrote:
> On Tue, 16 Jun 2020 14:19:01 -0700 Roman Gushchin <guro@fb.com> wrote:
>
> > >
> > > This version is based on top of v6 of the new slab controller
> > > patchset. The following patches are actually required by this series:
> > > mm: memcg: factor out memcg- and lruvec-level changes out of __mod_lruvec_state()
> > > mm: memcg: prepare for byte-sized vmstat items
> > > mm: memcg: convert vmstat slab counters to bytes
> > > mm: slub: implement SLUB version of obj_to_index()
> > > mm: memcontrol: decouple reference counting from page accounting
> > > mm: memcg/slab: obj_cgroup API
> >
> > Hello, Andrew!
> >
> > How this patchset should be routed: through the mm or percpu tree?
> >
> > It has been acked by Dennis (the percpu maintainer), but it does depend
> > on first several patches from the slab controller rework patchset.
>
> I can grab both.
Perfect, thanks!
>
> > The slab controller rework is ready to be merged: as in v6 most patches
> > in the series were acked by Johannes and/or Vlastimil and no questions
> > or concerns were raised after v6.
> >
> > Please, let me know if you want me to resend both patchsets.
>
> There was quite a bit of valuable discussion in response to [0/n] which
> really should have been in the changelog[s] from day one.
> slab-vs-slub, performance testing, etc.
>
> So, umm, I'll take a look at both series now but I do think an enhanced
> [0/n] description is warranted?
>
Yes, I'm running suggested tests right now, and will update on the results.
Thanks!
prev parent reply other threads:[~2020-06-17 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 23:08 Roman Gushchin
2020-06-08 23:08 ` [PATCH v2 1/5] percpu: return number of released bytes from pcpu_free_area() Roman Gushchin
2020-06-08 23:08 ` [PATCH v2 2/5] mm: memcg/percpu: account percpu memory to memory cgroups Roman Gushchin
2020-06-08 23:08 ` [PATCH v2 3/5] mm: memcg/percpu: per-memcg percpu memory statistics Roman Gushchin
2020-06-22 1:48 ` Nathan Chancellor
2020-06-22 3:26 ` Roman Gushchin
2020-06-22 3:51 ` Nathan Chancellor
2020-06-08 23:08 ` [PATCH v2 4/5] mm: memcg: charge memcg percpu memory to the parent cgroup Roman Gushchin
2020-06-08 23:08 ` [PATCH v2 5/5] kselftests: cgroup: add perpcu memory accounting test Roman Gushchin
2020-06-16 21:19 ` [Potential Spoof] [PATCH v2 0/5] mm: memcg accounting of percpu memory Roman Gushchin
2020-06-17 20:39 ` Andrew Morton
2020-06-17 20:47 ` Roman Gushchin [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=20200617204705.GA24694@carbon.DHCP.thefacebook.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.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