linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Jonghyeon Kim <tome01@ajou.ac.kr>
Cc: SeongJae Park <sj@kernel.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 0/3] Add NUMA-aware DAMOS watermarks
Date: Tue, 21 May 2024 18:00:34 -0700	[thread overview]
Message-ID: <20240522010034.79165-1-sj@kernel.org> (raw)
In-Reply-To: <20240520143038.189061-1-tome01@ajou.ac.kr>

Hi Jonghyeon,

On Mon, 20 May 2024 14:30:35 +0000 Jonghyeon Kim <tome01@ajou.ac.kr> wrote:

> Current DAMOS schemes are not considered with multiple NUMA memory nodes.
> For example, If we want to proactively reclaim memory of a one NUMA node,
> DAMON_RECLAIM has to wake up kdamond before kswapd does reclaim memory.
> However, since the DAMON watermarks are based on not a one NUMA memory
> node but total system free memory, kdamond is not waked up before invoking
> memory reclamation from kswapd of the target node.
> 
> These patches allow for DAMON to select monitoring target either total
> memory or a specific NUMA memory node.

I feel such usage could exist, but my humble brain is not clearly imagining
such realistic usage.  If you could further clarify the exampected usage, it
would be very helpful for me to better understand the intention and pros/cons
of this patchset.  Especially, I'm wondering why they would want to use the
watermark feature, rather than manually checking the metric and turning DAMON
on/off, or feeding the metric as a quota tuning goal.

> 
> ---
> Changes from RFC PATCH v1
> (https://lore.kernel.org/all/20220218102611.31895-1-tome01@ajou.ac.kr)
> - Add new metric type for NUMA node, DAMOS_WMARK_NODE_FREE_MEM_RATE
> - Drop commit about damon_start()
> - Support DAMON_LRU_SORT
> 
> Jonghyeon Kim (3):
>   mm/damon: Add new metric type and target node for watermark
>   mm/damon: add module parameters for NUMA system
>   mm/damon: add NUMA-awareness to DAMON modules

Following up to the above question, why they would want to use DAMON modules
rather than manually controlling DAMON via DAMON sysfs interface?


Thanks,
SJ

> 
>  include/linux/damon.h     | 11 +++++++++--
>  mm/damon/core.c           | 11 ++++++++---
>  mm/damon/lru_sort.c       | 14 ++++++++++++++
>  mm/damon/modules-common.h |  4 +++-
>  mm/damon/reclaim.c        | 14 ++++++++++++++
>  mm/damon/sysfs-schemes.c  | 35 +++++++++++++++++++++++++++++++++--
>  6 files changed, 81 insertions(+), 8 deletions(-)
> 
> -- 
> 2.34.1


  parent reply	other threads:[~2024-05-22  1:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 14:30 Jonghyeon Kim
2024-05-20 14:30 ` [RFC PATCH v2 1/3] mm/damon: Add new metric type and target node for watermark Jonghyeon Kim
2024-05-20 14:30 ` [RFC PATCH v2 2/3] mm/damon: add module parameters for NUMA system Jonghyeon Kim
2024-05-20 14:30 ` [RFC PATCH v2 3/3] mm/damon: add NUMA-awareness to DAMON modules Jonghyeon Kim
2024-05-22  1:00 ` SeongJae Park [this message]
2024-05-24  5:24   ` [RFC PATCH v2 0/3] Add NUMA-aware DAMOS watermarks Jonghyeon Kim
2024-05-25 17:47     ` SeongJae Park

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=20240522010034.79165-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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