[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250703052831.39709-1-sj@kernel.org>
Date: Wed, 2 Jul 2025 22:28:31 -0700
From: SeongJae Park <sj@...nel.org>
To: Yunjeong Mun <yunjeong.mun@...com>
Cc: SeongJae Park <sj@...nel.org>,
akpm@...ux-foundation.org,
damon@...ts.linux.dev,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
kernel_team@...ynix.com,
honggyu.kim@...com
Subject: Re: [RFC PATCH 2/2] samples/damon: add `migrate_hot` and `migrate_cold` knobs
On Thu, 3 Jul 2025 14:18:34 +0900 Yunjeong Mun <yunjeong.mun@...com> wrote:
> Hello SeongJae,
>
> On Tue, 1 Jul 2025 17:08:25 -0700 SeongJae Park <sj@...nel.org> wrote:
> > Hello Yunjeong,
> >
> > On Tue, 1 Jul 2025 17:54:17 +0900 Yunjeong Mun <yunjeong.mun@...com> wrote:
[...]
> > Because mtier is a sample code, I think it's primary goal is to help developers
> > know how they can use DAMON API functions for writing kernel code that is
> > required for a situation similar to the sample. Hence the sample should be
> > clean and simple enough to be understood.
>
> Thanks for explanation. I understand the intention of mtier module.
> As you mentioned, mtier is helpful for leraning how to configure and
> run DAMON.
Glad to hear this sample is working for the intended goal!
[...]
> > But, I feel like this change is rather making code too longer and complicated.
> > Hence I would suggest dropping this patch if you agree. Please let me know if
> > you have different opinions, or I'm missing something.
> >
>
> Ok, I will drop this patch in next version RFC. As you mentiond, mtier
> module should be simple and intuitive enough. I will consider this
> kind of tiering module to mm/damon. I'll send you RFC v2 soon.
Thank you for kindly accepting my suggestion. Looking forward to the next
patches!
Thanks,
SJ
[...]
Powered by blists - more mailing lists