linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Cai Xinchen <caixinchen1@huawei.com>
Cc: songmuchun@bytedance.com, akpm@linux-foundation.org,
	hannes@cmpxchg.org, longman@redhat.com, mhocko@kernel.org,
	roman.gushchin@linux.dev, shakeelb@google.com,
	cgroups@vger.kernel.org, duanxiongchun@bytedance.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	yosryahmed@google.com, mpenttil@redhat.com
Subject: Re: [PATCH 0/1] Fix vmstat_percpu incorrect subtraction after reparent
Date: Fri, 24 Mar 2023 18:14:11 +0100	[thread overview]
Message-ID: <20230324171411.t2romq3ydphoonu2@blackpad> (raw)
In-Reply-To: <20230320030648.50663-1-caixinchen1@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

On Mon, Mar 20, 2023 at 03:06:47AM +0000, Cai Xinchen <caixinchen1@huawei.com> wrote:
> There are two problems left:
> 
>      root
>      /  \
>     A    B
>    / \    \
>   C   E    D
> 
> 1. In some case of reparent, some page cache may be used by other memcg
> D but it charges to the parent memcg A of dying memcg E. D is getting
> away with using the page for free while A is taxed.

Note that A is (effectively) taxed even before E is removed due to
hierarchical nature of charging. Then what you describe transforms into
"well-known" problem of shared charging (with not well-known solution
:-/).

HTH,
Michal

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2023-03-24 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  3:06 Cai Xinchen
2023-03-20  3:06 ` [PATCH 1/1] mm: memcontrol: fix vmstats_percpu state " Cai Xinchen
2023-03-24 17:11   ` Michal Koutný
2023-03-27  1:29     ` Cai Xinchen
2023-03-24 17:14 ` Michal Koutný [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=20230324171411.t2romq3ydphoonu2@blackpad \
    --to=mkoutny@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=caixinchen1@huawei.com \
    --cc=cgroups@vger.kernel.org \
    --cc=duanxiongchun@bytedance.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=mhocko@kernel.org \
    --cc=mpenttil@redhat.com \
    --cc=roman.gushchin@linux.dev \
    --cc=shakeelb@google.com \
    --cc=songmuchun@bytedance.com \
    --cc=yosryahmed@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