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
Subject: Re: [PATCH] mm/damon: modified damon_call_control from static to kmalloc
Date: Tue, 9 Dec 2025 18:54:00 -0800 [thread overview]
Message-ID: <20251210025400.51467-1-sj@kernel.org> (raw)
In-Reply-To: <CAHOvCC6_-h1jQkZMbtYDC_jrB490jzp1t1Fx-_mhYnE7tqvzbw@mail.gmail.com>
On Tue, 9 Dec 2025 21:20:42 +0900 JaeJoon Jung <rgbi3307@gmail.com> wrote:
> Hello, SeongJae,
>
> Thank you for your detailed feedback.
> My patch has the advantage of removing the use of
> the damon_call_control.dealloc_on_cancel variable.
Thank you for keeping this conversation for enlightening me, Jaejoon.
Could you please elaborate why you think the removal is an advantage? I
understand reducing code is good in general. But that's only if the code is
unnecessary. dealloc_on_cancel is there for real use case, so I don't clearly
see why it is an advantage.
Meanwhile I find the feature might look complicated, or not well documented.
Specifically, dealloc_on_cancel should be set on only dynamic-allocated
damon_call_control object, but that is not well documented on the kernel-doc
comments. Are you saying removing it is an advantage because it makes reading
code easier? If that's the case, how about improving the documentation?
Btw, please consider not doing "top posting" [1].
[1] https://subspace.kernel.org/etiquette.html#do-not-top-post-when-replying
Thanks,
SJ
[...]
prev parent reply other threads:[~2025-12-10 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 22:47 JaeJoon Jung
2025-12-07 2:36 ` SeongJae Park
2025-12-09 12:20 ` JaeJoon Jung
2025-12-10 2:54 ` 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=20251210025400.51467-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux-mm@kvack.org \
--cc=rgbi3307@gmail.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