From: SeongJae Park <sj@kernel.org>
To: Jonghyeon Kim <tome01@ajou.ac.kr>
Cc: akpm@linux-foundation.org, Jonathan.Cameron@Huawei.com,
amit@kernel.org, benh@kernel.crashing.org, corbet@lwn.net,
david@redhat.com, dwmw@amazon.com, elver@google.com,
foersleo@amazon.de, gthelen@google.com, markubo@amazon.de,
rientjes@google.com, shakeelb@google.com, shuah@kernel.org,
linux-damon@amazon.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 0/3] Rebase DAMON_RECALIM for NUMA system
Date: Tue, 22 Feb 2022 09:53:02 +0000 [thread overview]
Message-ID: <20220222095302.7859-1-sj@kernel.org> (raw)
In-Reply-To: <20220218102611.31895-1-tome01@ajou.ac.kr>
Hello Jonghyeon,
On Fri, 18 Feb 2022 19:26:08 +0900 Jonghyeon Kim <tome01@ajou.ac.kr> wrote:
>
> Current DAMON_RECALIM is not compatible with the NUMA memory system. To
> proactively reclaim memory, DAMON_RECLAIM kernel thread(kdamond) has to wake up
> before kswapd does reclaim memory. However, the current watermark for proactive
> reclamation is based on entire system free memory. So, though the one memory
> node is fully used, kdamond is not waked up.
>
> These patches clarify watermarks of DAMOS and enable monitoring per NUMA node
> proactive reclamation on DAMON_RECLAIM.
The high level concept of this patchset looks good to me. Nevertheless, maybe
there is some rooms for improvement. I left some comments on patches.
Thanks,
SJ
>
> Jonghyeon Kim (3):
> mm/damon: Rebase damos watermarks for NUMA systems
> mm/damon/core: Add damon_start_one()
> mm/damon/reclaim: Add per NUMA node proactive reclamation by
> DAMON_RECLAIM.
>
> include/linux/damon.h | 3 +
> mm/damon/core.c | 39 +++++++++--
> mm/damon/reclaim.c | 147 ++++++++++++++++++++++++++++++------------
> 3 files changed, 140 insertions(+), 49 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2022-02-22 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 10:26 Jonghyeon Kim
2022-02-18 10:26 ` [RFC PATCH v1 1/3] mm/damon: Rebase damos watermarks for NUMA systems Jonghyeon Kim
2022-02-22 9:53 ` SeongJae Park
[not found] ` <20220223051056.GA3502@swarm08>
2022-02-23 7:10 ` Jonghyeon Kim
2022-02-18 10:26 ` [RFC PATCH v1 2/3] mm/damon/core: Add damon_start_one() Jonghyeon Kim
2022-02-22 9:53 ` SeongJae Park
[not found] ` <20220223051113.GA3535@swarm08>
2022-02-23 7:11 ` Jonghyeon Kim
2022-02-18 10:26 ` [RFC PATCH v1 3/3] mm/damon/reclaim: Add per NUMA node proactive reclamation by DAMON_RECLAIM Jonghyeon Kim
2022-02-22 9:53 ` SeongJae Park
[not found] ` <20220223051127.GA3588@swarm08>
2022-02-23 7:12 ` Jonghyeon Kim
2022-02-22 9:53 ` SeongJae Park [this message]
[not found] ` <20220223051146.GA4530@swarm08>
2022-02-23 7:12 ` [RFC PATCH v1 0/3] Rebase DAMON_RECALIM for NUMA system Jonghyeon Kim
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=20220222095302.7859-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=akpm@linux-foundation.org \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=elver@google.com \
--cc=foersleo@amazon.de \
--cc=gthelen@google.com \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markubo@amazon.de \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=tome01@ajou.ac.kr \
/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