From: Roman Gushchin <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>
To: "Michal Koutný" <mkoutny-IBi9RG/b67k@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Michal Hocko <mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Shakeel Butt <shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kselftest-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Richard Palethorpe <rpalethorpe-l3A5Bk7waGM@public.gmane.org>
Subject: Re: [PATCH v2 4/5] selftests: memcg: Remove protection from top level memcg
Date: Wed, 18 May 2022 12:10:49 -0700 [thread overview]
Message-ID: <YoVEuWwZACdfkEvF@carbon> (raw)
In-Reply-To: <20220518161859.21565-5-mkoutny-IBi9RG/b67k@public.gmane.org>
On Wed, May 18, 2022 at 06:18:58PM +0200, Michal Koutny wrote:
> The reclaim is triggered by memory limit in a subtree, therefore the
> testcase does not need configured protection against external reclaim.
>
> Also, correct respective comments
>
> Signed-off-by: Michal Koutný <mkoutny-IBi9RG/b67k@public.gmane.org>
Acked-by: Roman Gushchin <roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org>
WARNING: multiple messages have this Message-ID (diff)
From: Roman Gushchin <roman.gushchin@linux.dev>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Shakeel Butt <shakeelb@google.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Richard Palethorpe <rpalethorpe@suse.de>
Subject: Re: [PATCH v2 4/5] selftests: memcg: Remove protection from top level memcg
Date: Wed, 18 May 2022 12:10:49 -0700 [thread overview]
Message-ID: <YoVEuWwZACdfkEvF@carbon> (raw)
In-Reply-To: <20220518161859.21565-5-mkoutny@suse.com>
On Wed, May 18, 2022 at 06:18:58PM +0200, Michal Koutny wrote:
> The reclaim is triggered by memory limit in a subtree, therefore the
> testcase does not need configured protection against external reclaim.
>
> Also, correct respective comments
>
> Signed-off-by: Michal Koutný <mkoutny@suse.com>
Acked-by: Roman Gushchin <roman.gushchin@linux.dev>
next prev parent reply other threads:[~2022-05-18 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 16:18 Michal Koutný
[not found] ` <20220518161859.21565-1-mkoutny-IBi9RG/b67k@public.gmane.org>
2022-05-18 16:18 ` [PATCH v2 1/5] selftests: memcg: Fix compilation Michal Koutný
2022-05-18 16:18 ` Michal Koutný
[not found] ` <20220518161859.21565-2-mkoutny-IBi9RG/b67k@public.gmane.org>
2022-05-21 14:11 ` Muhammad Usama Anjum
2022-05-21 14:11 ` Muhammad Usama Anjum
[not found] ` <5242b7ab-d6b6-55d4-c211-ec27293be795-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2022-05-23 13:29 ` Michal Koutný
2022-05-23 13:29 ` Michal Koutný
2022-05-18 16:18 ` [PATCH v2 2/5] selftests: memcg: Expect no low events in unprotected sibling Michal Koutný
2022-05-18 16:18 ` Michal Koutný
2022-05-18 16:18 ` [PATCH v2 3/5] selftests: memcg: Adjust expected reclaim values of protected cgroups Michal Koutný
2022-05-18 16:18 ` Michal Koutný
[not found] ` <20220518161859.21565-4-mkoutny-IBi9RG/b67k@public.gmane.org>
2022-05-18 19:10 ` Roman Gushchin
2022-05-18 19:10 ` Roman Gushchin
2022-05-18 16:18 ` [PATCH v2 4/5] selftests: memcg: Remove protection from top level memcg Michal Koutný
2022-05-18 16:18 ` Michal Koutný
[not found] ` <20220518161859.21565-5-mkoutny-IBi9RG/b67k@public.gmane.org>
2022-05-18 19:10 ` Roman Gushchin [this message]
2022-05-18 19:10 ` Roman Gushchin
2022-05-18 16:18 ` [PATCH v2 5/5] selftests: memcg: Factor out common parts of memory.{low,min} tests Michal Koutný
2022-05-18 16:18 ` Michal Koutný
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=YoVEuWwZACdfkEvF@carbon \
--to=roman.gushchin-fxuvxftifdnyg1zeobxtfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kselftest-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=mkoutny-IBi9RG/b67k@public.gmane.org \
--cc=rpalethorpe-l3A5Bk7waGM@public.gmane.org \
--cc=shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
/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.