linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Quanmin Yan <yanquanmin1@huawei.com>
To: SeongJae Park <sj@kernel.org>
Cc: <akpm@linux-foundation.org>, <damon@lists.linux.dev>,
	<linux-mm@kvack.org>, <enze.li@gmx.com>, <sunnanyong@huawei.com>,
	Enze Li <lienze@kylinos.cn>
Subject: Re: [PATCH] mm/damon: unify address range representation with damon_addr_range
Date: Fri, 30 Jan 2026 10:26:53 +0800	[thread overview]
Message-ID: <d6f2b111-bb42-4437-9711-bf06cf9afefa@huawei.com> (raw)
In-Reply-To: <20260129161029.48991-1-sj@kernel.org>

Hi SJ,

[...]

> Actually, there is another bug that need to be fixed.  Nonetheless, that's
> orthogonal to this patch, so it is not a blocker of this patch in my opinion.

Are you referring to the scenario where, on a 32-bit system with LPAE 
support, the biggest System RAM address found exceeds the range of 
unsigned long? Actually, DAMON only actively searches for the biggest 
System RAM address when the user does not set a monitoring region. In 
this case, we always reset addr_unit to 1, which essentially restricts 
DAMON’s monitorable address range to 0–UL. Therefore, the described 
situation does not occur. For details, please refer to commit [1]. 
However, we could perhaps further optimize this by finding any biggest 
System RAM address, setting damon_addr_range, and dynamically adjusting 
addr_unit. However, there are currently no specific requirements for 
this, so this work has been temporarily put on hold. [1] commit 
dfc02531f413 ("mm/damon/reclaim: use min_sz_region for core address 
alignment when setting regions") Thanks, Quanmin Yan

[...]



  reply	other threads:[~2026-01-30  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 10:08 Enze Li
2026-01-29 16:10 ` SeongJae Park
2026-01-30  2:26   ` Quanmin Yan [this message]
2026-01-30  3:07     ` Quanmin Yan
2026-01-30  3:38       ` SeongJae Park
2026-01-31  1:56         ` 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=d6f2b111-bb42-4437-9711-bf06cf9afefa@huawei.com \
    --to=yanquanmin1@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=enze.li@gmx.com \
    --cc=lienze@kylinos.cn \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.org \
    --cc=sunnanyong@huawei.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