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 2/3] selftests: cgroup: refactor proactive reclaim code to reclaim_until()
Date: Wed, 23 Nov 2022 17:03:39 -0800 [thread overview]
Message-ID: <Y37C68kUYakRQ2ZC@P9FQF9L96D.corp.robot.car> (raw)
In-Reply-To: <20221123092132.2521764-3-yosryahmed@google.com>
On Wed, Nov 23, 2022 at 09:21:31AM +0000, Yosry Ahmed wrote:
> Refactor the code that drives writing to memory.reclaim (retrying, error
> handling, etc) from test_memcg_reclaim() to a helper called
> reclaim_until(), which proactively reclaims from a memcg until its
> usage reaches a certain value.
>
> This will be used in a following patch in another test.
>
> Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
> ---
> .../selftests/cgroup/test_memcontrol.c | 85 +++++++++++--------
> 1 file changed, 49 insertions(+), 36 deletions(-)
>
> diff --git a/tools/testing/selftests/cgroup/test_memcontrol.c b/tools/testing/selftests/cgroup/test_memcontrol.c
> index 8833359556f3..d4182e94945e 100644
> --- a/tools/testing/selftests/cgroup/test_memcontrol.c
> +++ b/tools/testing/selftests/cgroup/test_memcontrol.c
> @@ -645,6 +645,53 @@ static int test_memcg_max(const char *root)
> return ret;
The code below looks correct, but can be simplified a bit.
And btw thank you for adding a test!
Reviewed-by: Roman Gushchin <roman.gushchin@linux.dev>
(idk if you want invest your time in further simplication of this code,
it was this way before this patch, so up to you).
> }
>
> +/* Reclaim from @memcg until usage reaches @goal_usage */
> +static bool reclaim_until(const char *memcg, long goal_usage)
> +{
> + char buf[64];
> + int retries = 5;
> + int err;
> + long current, to_reclaim;
> +
> + /* Nothing to do here */
> + if (cg_read_long(memcg, "memory.current") <= goal_usage)
> + return true;
> +
> + while (true) {
> + current = cg_read_long(memcg, "memory.current");
> + to_reclaim = current - goal_usage;
> +
> + /*
> + * We only keep looping if we get -EAGAIN, which means we could
> + * not reclaim the full amount. This means we got -EAGAIN when
> + * we actually reclaimed the requested amount, so fail.
> + */
> + if (to_reclaim <= 0)
> + break;
> +
> + snprintf(buf, sizeof(buf), "%ld", to_reclaim);
> + err = cg_write(memcg, "memory.reclaim", buf);
> + if (!err) {
> + /*
> + * If writing succeeds, then the written amount should have been
> + * fully reclaimed (and maybe more).
> + */
> + current = cg_read_long(memcg, "memory.current");
> + if (!values_close(current, goal_usage, 3) && current > goal_usage)
> + break;
There are 3 places in this function where memory.current is read and compared
to goal_usage. I believe only one can be left.
> + return true;
> + }
> +
> + /* The kernel could not reclaim the full amount, try again. */
> + if (err == -EAGAIN && retries--)
> + continue;
> +
> + /* We got an unexpected error or ran out of retries. */
> + break;
if (err != -EAGAIN || retries--)
break;
Thanks!
next prev parent reply other threads:[~2022-11-24 1:03 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 [this message]
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
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=Y37C68kUYakRQ2ZC@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
all inboxes | Powered by JetHome®