From: Michal Hocko <mhocko@suse.com>
To: Guopeng Zhang <guopeng.zhang@linux.dev>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Guopeng Zhang <zhangguopeng@kylinos.cn>
Subject: Re: [PATCH] mm: memcg: stop reclaim when a limit update is superseded
Date: Wed, 29 Jul 2026 10:02:22 +0200 [thread overview]
Message-ID: <ammzjkUIADCxO2mP@tiehlicka> (raw)
In-Reply-To: <f706d139-53a7-436d-adc5-c691577ce53b@linux.dev>
On Wed 29-07-26 14:15:25, Guopeng Zhang wrote:
>
>
> 在 2026/7/27 21:58, Michal Hocko 写道:
> > On Mon 27-07-26 20:59:23, Guopeng Zhang wrote:
> >>
> >>
> >> 在 2026/7/27 16:16, Michal Hocko 写道:
> >>> On Fri 24-07-26 10:18:05, Guopeng Zhang wrote:
[...]
> > Is this trying to replicate any real workload? One would expect that
> > writers to limit do some sort of coordination otherwise the exact
> > behavior is not really well defined.
> >
>
> No, this was not motivated by a reported production workload. We found
> it through automated randomized testing for our cgroup observability
> work and reduced it to the reproducer above.
This is an important detail to be mentioned in the changelog. Describing
motivation for a change is really important, especially if it has direct
impact in user interface behavior.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2026-07-29 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 2:18 [PATCH] mm: memcg: stop reclaim when a limit update is superseded Guopeng Zhang
2026-07-24 3:32 ` Tao Cui
2026-07-24 6:53 ` Guopeng Zhang
2026-07-26 3:42 ` Andrew Morton
2026-07-26 5:57 ` Guopeng Zhang
2026-07-27 8:16 ` Michal Hocko
2026-07-27 12:59 ` Guopeng Zhang
2026-07-27 13:58 ` Michal Hocko
2026-07-29 6:15 ` Guopeng Zhang
2026-07-29 8:02 ` Michal Hocko [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=ammzjkUIADCxO2mP@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=guopeng.zhang@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=zhangguopeng@kylinos.cn \
/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.