From: SeongJae Park <sj@kernel.org>
To: JaeJoon Jung <rgbi3307@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, rgbi3307@nate.com
Subject: Re: [PATCH 1/2] mm/damon/core: modified and tunning damon_split_regions_of()
Date: Wed, 14 Jan 2026 07:46:21 -0800 [thread overview]
Message-ID: <20260114154622.100466-1-sj@kernel.org> (raw)
In-Reply-To: <20260113121646.31441-1-rgbi3307@gmail.com>
Hello JaeJoon, thank you for continued interest in DAMON.
On Tue, 13 Jan 2026 21:16:42 +0900 JaeJoon Jung <rgbi3307@gmail.com> wrote:
> Before modification:
> sz_region
> |--------|--------|--------||--------|--------|--------|--------|
> nr_subs: 1 2 3 4 5 9
> split random: <----------- (*] randmon LOST -------------->
>
> When dividing sz_region at rand, the random value may be small, such as
> 1 or 2. At this time, there is a problem that only the front areas
> corresponding to 1 and 2 are divided, and the remaining back area
> becomes too wide. If the area is too wide, there will be many missed
> address access judgments.
>
> After modification:
> sz_region
> |--------|--------|--------|--------|--------|--------|--------||
> nr_subs: 1 2 3 4 5 9
> split from <------------ (sz_region / nr_subs) ------------------>
>
> It is recommended to divide sz_region evenly in the ratio (sz_region /
> nr_subs) rather than using rand. In this way, if you decide nr_subs well,
> you can logically match the number of divisions and their sizes.
I was thinking about how to reply to this patch. Since it is taking unusually
long time, let me add short comments for direct future of this patch.
The existing code uses random() for a reason. This change might break it. Can
you further explain what was the point of the use of random(), and why this
change is not breaking it?
>
> Signed-off-by: JaeJoon Jung <rgbi3307@gmail.com>
Unless you can give me a convincing answer to my above question,
Nacked-by: SeongJae Park <sj@kernel.org>
Same for your followup patch [1]. Btw, please send patches of same series as
one thread from next time.
[1] https://lore.kernel.org/20260113121731.31468-1-rgbi3307@gmail.com
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-01-14 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 12:16 JaeJoon Jung
2026-01-14 15:46 ` SeongJae Park [this message]
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=20260114154622.100466-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rgbi3307@gmail.com \
--cc=rgbi3307@nate.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