All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: "Michal Koutný" <mkoutny@suse.com>,
	"Michal Hocko" <mhocko@suse.com>, "Roman Gushchin" <guro@fb.com>,
	"Shakeel Butt" <shakeelb@google.com>,
	"Seth Jennings" <sjenning@redhat.com>,
	"Dan Streetman" <ddstreet@ieee.org>,
	"Minchan Kim" <minchan@kernel.org>,
	linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 6/6] zswap: memcg accounting
Date: Tue, 17 May 2022 16:52:16 -0700	[thread overview]
Message-ID: <20220517165216.7acd8434f8b25606836e21e6@linux-foundation.org> (raw)
In-Reply-To: <YoKtgaxOAMBVKiCf@cmpxchg.org>

On Mon, 16 May 2022 16:01:05 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:

> > > Flushing unnecessary groups with a ratelimit doesn't sound like an
> > > improvement to me.
> > 
> > Then I'm only concerned about a situation when there's a single deep
> > memcg that undergoes both workingset_refault() and zswap querying.
> > The latter (bare call to cgroup_rstat_flush()) won't reset
> > stats_flush_threshold, so the former (or the async flush more likely)
> > would attempt a flush too. The flush work (on the leaf memcg) would be
> > done twice even though it may be within the tolerance of cumulated
> > error the second time.
> > 
> > This is a thing that might require attention in the future (depending on
> > some data how it actually performs). I see how the current approach is
> > justified.
> 
> Yes, we can optimize it should the need arise. So far it's been fine.
> 
> Thanks for your thoughts, Michal.

Me too.

I think everything is settled here so I plan to import this series into
mm-stable in a couple of days.

at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/

 documentation-filesystems-proc-update-meminfo-section.patch
 documentation-filesystems-proc-update-meminfo-section-fix.patch
 documentation-filesystems-proc-update-meminfo-section-fix-2.patch
 mm-kconfig-move-swap-and-slab-config-options-to-the-mm-section.patch
 mm-kconfig-group-swap-slab-hotplug-and-thp-options-into-submenus.patch
 mm-kconfig-group-swap-slab-hotplug-and-thp-options-into-submenus-fix.patch
 mm-kconfig-group-swap-slab-hotplug-and-thp-options-into-submenus-fix-fix.patch
 mm-kconfig-simplify-zswap-configuration.patch
 mm-zswap-add-basic-meminfo-and-vmstat-coverage.patch
 zswap-memcg-accounting.patch
 zswap-memcg-accounting-fix.patch
 zswap-memcg-accounting-fix-2.patch



  reply	other threads:[~2022-05-17 23:52 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 15:28 [PATCH v2 0/6] zswap: accounting & cgroup control Johannes Weiner
2022-05-10 15:28 ` Johannes Weiner
2022-05-10 15:28 ` [PATCH v2 1/6] Documentation: filesystems: proc: update meminfo section Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-11 17:11   ` David Hildenbrand
2022-05-11 17:11     ` David Hildenbrand
2022-05-11 18:51     ` Johannes Weiner
2022-05-11 18:51       ` Johannes Weiner
2022-05-12  8:55       ` David Hildenbrand
2022-05-12  8:55         ` David Hildenbrand
2022-05-10 15:28 ` [PATCH v2 2/6] mm: Kconfig: move swap and slab config options to the MM section Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-10 15:28 ` [PATCH v2 3/6] mm: Kconfig: group swap, slab, hotplug and thp options into submenus Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-10 22:40   ` Andrew Morton
2022-05-10 22:40     ` Andrew Morton
2022-05-11 15:22     ` Johannes Weiner
2022-05-11 15:22       ` Johannes Weiner
2022-05-11 16:28       ` Johannes Weiner
2022-05-11 16:28         ` Johannes Weiner
2022-05-10 15:28 ` [PATCH v2 4/6] mm: Kconfig: simplify zswap configuration Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-10 15:28 ` [PATCH v2 5/6] mm: zswap: add basic meminfo and vmstat coverage Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-11 17:13   ` David Hildenbrand
2022-05-11 17:13     ` David Hildenbrand
2022-05-10 15:28 ` [PATCH v2 6/6] zswap: memcg accounting Johannes Weiner
2022-05-10 15:28   ` Johannes Weiner
2022-05-11 17:32   ` Michal Koutný
2022-05-11 17:32     ` Michal Koutný
2022-05-11 19:06     ` Johannes Weiner
2022-05-11 19:06       ` Johannes Weiner
2022-05-13 15:14       ` Michal Koutný
2022-05-13 15:14         ` Michal Koutný
2022-05-13 17:08         ` Johannes Weiner
2022-05-13 17:08           ` Johannes Weiner
2022-05-16 14:34           ` Michal Koutný
2022-05-16 14:34             ` Michal Koutný
2022-05-16 20:01             ` Johannes Weiner
2022-05-16 20:01               ` Johannes Weiner
2022-05-17 23:52               ` Andrew Morton [this message]
2022-05-18  8:23                 ` Michal Koutný
2022-05-18  8:23                   ` Michal Koutný
2022-05-13 17:23   ` Shakeel Butt
2022-05-13 17:23     ` Shakeel Butt
2022-05-13 18:25     ` Johannes Weiner
2022-05-13 18:25       ` Johannes Weiner

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=20220517165216.7acd8434f8b25606836e21e6@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=ddstreet@ieee.org \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=mkoutny@suse.com \
    --cc=shakeelb@google.com \
    --cc=sjenning@redhat.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.