From: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
To: SeongJae Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<damon@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [RFC PATCH 02/19] mm/damon/core: embed damon_probe objects in damon_ctx
Date: Tue, 28 Apr 2026 16:09:34 +0300 [thread overview]
Message-ID: <2d2415b3-d7e8-4b8d-aaad-c4fd27eb18f8@huawei-partners.com> (raw)
In-Reply-To: <20260428003559.113178-1-sj@kernel.org>
On 4/28/2026 3:35 AM, SeongJae Park wrote:
> On Mon, 27 Apr 2026 16:18:14 +0300 Gutierrez Asier <gutierrez.asier@huawei-partners.com> wrote:
>
>>
>>
>> On 4/26/2026 11:52 PM, SeongJae Park wrote:
>>> Let damon_probe objects be able to be installed on a given damon_ctx, by
>>> adding a linked list header for storing the objects. Add initialization
>>> and cleanup of the new field with helper functions, too.
>>>
>>> Signed-off-by: SeongJae Park <sj@kernel.org>
> [...]
>>> +static void damon_del_probe(struct damon_probe *p)
>>> +{
>>> + list_del(&p->list);
>>> +}
>>> +
>>> +static void damon_free_probe(struct damon_probe *p)
>>> +{
>>> + kfree(p);
>>> +}
>>> +
>>> +static void damon_destroy_probe(struct damon_probe *p)
>>> +{
>>> + damon_del_probe(p);
>>> + damon_free_probe(p);
>>
>> Why don't we inline list_del and kfree here instead of calling
>> damon_del/free_probe?
>
> I want to hide the fact that we are using linked list. This abstraction also
> makes it easy to control the calling paths of the data structure manipulation.
> Meanwhile, smart enough compilers could inline these if it helps.
I see your point. It make sense.
>
> Thanks,
> SJ
>
> [...]
>
--
Asier Gutierrez
Huawei
next prev parent reply other threads:[~2026-04-28 13:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-26 20:52 [RFC PATCH 00/19] mm/damon: introduce data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 01/19] mm/damon/core: introduce struct damon_probe SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 02/19] mm/damon/core: embed damon_probe objects in damon_ctx SeongJae Park
2026-04-27 13:18 ` Gutierrez Asier
2026-04-28 0:35 ` SeongJae Park
2026-04-28 13:09 ` Gutierrez Asier [this message]
2026-04-26 20:52 ` [RFC PATCH 03/19] mm/damon/core: introduce damon_filter SeongJae Park
2026-05-09 18:11 ` SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 04/19] mm/damon/core: commit probes SeongJae Park
2026-04-27 13:21 ` Gutierrez Asier
2026-04-28 0:39 ` SeongJae Park
2026-04-28 13:13 ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 05/19] mm/damon/core: introduce damon_region->probe_hits SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 06/19] mm/damon/core: introduce damon_ops->apply_probes SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 07/19] mm/damon/core: do data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 08/19] mm/damon/paddr: support " SeongJae Park
2026-05-09 18:08 ` SeongJae Park
2026-05-11 0:35 ` SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 09/19] mm/damon/sysfs: implement probes dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 10/19] mm/damon/sysfs: implement probe dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 11/19] mm/damon/sysfs: implement filters directory SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 12/19] mm/damon/sysfs: implement filter dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 13/19] mm/damon/sysfs: implement filter dir files SeongJae Park
2026-04-27 13:24 ` Gutierrez Asier
2026-04-28 0:44 ` SeongJae Park
2026-04-28 13:10 ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 14/19] mm/damon/sysfs: setup probes on DAMON core API parameters SeongJae Park
2026-04-27 13:25 ` Gutierrez Asier
2026-04-28 0:48 ` SeongJae Park
2026-04-28 13:08 ` Gutierrez Asier
2026-04-26 20:52 ` [RFC PATCH 15/19] mm/damon/sysfs-schemes: implement tried_region/probe_hits file SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 16/19] mm/damon: trace probe_hits SeongJae Park
2026-04-28 18:17 ` Steven Rostedt
2026-04-29 0:13 ` SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 17/19] selftests/damon/sysfs.sh: test probes dir SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 18/19] Docs/mm/damon/design: document data attributes monitoring SeongJae Park
2026-04-26 20:52 ` [RFC PATCH 19/19] Docs/admin-guide/mm/damon/usage: " SeongJae Park
2026-04-27 13:16 ` [RFC PATCH 00/19] mm/damon: introduce " Gutierrez Asier
2026-04-28 0:33 ` 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=2d2415b3-d7e8-4b8d-aaad-c4fd27eb18f8@huawei-partners.com \
--to=gutierrez.asier@huawei-partners.com \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@kernel.org \
/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