From: Roman Gushchin <roman.gushchin@linux.dev>
To: Yosry Ahmed <yosryahmed@google.com>
Cc: Shakeel Butt <shakeelb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.com>, Yu Zhao <yuzhao@google.com>,
Muchun Song <songmuchun@bytedance.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Vasily Averin <vasily.averin@linux.dev>,
Vlastimil Babka <vbabka@suse.cz>,
Chris Down <chris@chrisdown.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 3/3] selftests: cgroup: make sure reclaim target memcg is unprotected
Date: Wed, 23 Nov 2022 17:04:56 -0800 [thread overview]
Message-ID: <Y37DOJqKrFfFB2ZW@P9FQF9L96D.corp.robot.car> (raw)
In-Reply-To: <20221123092132.2521764-4-yosryahmed@google.com>
On Wed, Nov 23, 2022 at 09:21:32AM +0000, Yosry Ahmed wrote:
> Make sure that we ignore protection of a memcg that is the target of
> memcg reclaim.
>
> Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
> ---
> tools/testing/selftests/cgroup/test_memcontrol.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev>
Thank you!
prev parent reply other threads:[~2022-11-24 1:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 9:21 [PATCH v2 0/3] mm: memcg: fix protection of reclaim target memcg Yosry Ahmed
2022-11-23 9:21 ` [PATCH v2 1/3] mm: memcg: fix stale " Yosry Ahmed
2022-11-24 0:40 ` Roman Gushchin
2022-11-24 0:57 ` Yosry Ahmed
2022-11-23 9:21 ` [PATCH v2 2/3] selftests: cgroup: refactor proactive reclaim code to reclaim_until() Yosry Ahmed
2022-11-24 1:03 ` Roman Gushchin
2022-11-24 3:16 ` Yosry Ahmed
2022-11-29 19:42 ` Yosry Ahmed
2022-11-30 17:19 ` Roman Gushchin
2022-11-30 18:25 ` Yosry Ahmed
2022-12-02 3:19 ` Yosry Ahmed
2022-11-23 9:21 ` [PATCH v2 3/3] selftests: cgroup: make sure reclaim target memcg is unprotected Yosry Ahmed
2022-11-24 1:04 ` 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=Y37DOJqKrFfFB2ZW@P9FQF9L96D.corp.robot.car \
--to=roman.gushchin@linux.dev \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=vasily.averin@linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yosryahmed@google.com \
--cc=yuzhao@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