From: David Hildenbrand <david@redhat.com>
To: xhao@linux.alibaba.com, sj@kernel.org
Cc: rongwei.wang@linux.alibaba.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support
Date: Fri, 18 Mar 2022 09:29:20 +0100 [thread overview]
Message-ID: <5c46548a-04b9-607e-f43a-63545131d336@redhat.com> (raw)
In-Reply-To: <611f2ec6-04de-440a-3d54-c2bc34f45cf3@linux.alibaba.com>
On 18.03.22 06:13, xhao@linux.alibaba.com wrote:
>
> On 3/18/22 12:42 AM, David Hildenbrand wrote:
>> On 17.03.22 08:03, Xin Hao wrote:
>>> Hi David,
>>>
>>> On 3/16/22 11:09 PM, David Hildenbrand wrote:
>>>> On 15.03.22 17:37, Xin Hao wrote:
>>>>
>>>> s/minotor/monitor/
>>> Thanks, i will fix it.
>>>>> The purpose of these patches is to add CMA memory monitoring function.
>>>>> In some memory tight scenarios, it will be a good choice to release more
>>>>> memory by monitoring the CMA memory.
>>>> I'm sorry, but it's hard to figure out what the target use case should
>>>> be. Who will release CMA memory and how? Who will monitor that? What are
>>>> the "some memory tight scenarios"? What's the overall design goal?
>>> I may not be describing exactly what i mean,My intention is to find out
>>> how much of the reserved CMA space is actually used and which is unused,
>>> For those that are not used, I understand that they can be released by
>>> cma_release(). Of course, This is just a little personal thought that I
>>> think is helpful for saving memory.
>> Hm, not quite. We can place movable allocations on cma areas, to be
>> migrated away once required for allocations via CMA. So just looking at
>> the pages allocated within a CMA area doesn't really tell you what's
>> actually going on.
>
> I don't think so, the damon not looking at the pages allocate, It is
> constantly monitoring who is using CMA area pages through tracking page
> access bit
>
> in the kernel via the kdamond.x thread, So through damon, it can tell us
> about the hot and cold distribution of CMA memory.
I'm not sure I follow. With random movable pages being placed on the CMA
area, the mentioned use case of "cma_release()" to release pages doesn't
make sense to me.
I assume I'm missing the big picture -- and that should be properly
documented in the patch description. We don't add stuff just because it
could be used somehow, there should be a clear motivation how it can
actually be used.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-03-18 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:37 Xin Hao
2022-03-15 16:37 ` [RFC PATCH V1 1/3] mm/damon: rename damon_evenly_split_region() Xin Hao
2022-03-15 16:37 ` [RFC PATCH V1 2/3] mm/damon/paddr: Move "paddr" relative func to ops-common.c file Xin Hao
2022-03-15 16:37 ` [RFC PATCH V1 3/3] mm/damon/sysfs: Add CMA memory monitoring Xin Hao
2022-03-16 15:09 ` [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support David Hildenbrand
2022-03-17 7:03 ` Xin Hao
2022-03-17 16:42 ` David Hildenbrand
2022-03-18 5:13 ` xhao
2022-03-18 8:29 ` David Hildenbrand [this message]
2022-03-18 8:40 ` sj
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=5c46548a-04b9-607e-f43a-63545131d336@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongwei.wang@linux.alibaba.com \
--cc=sj@kernel.org \
--cc=xhao@linux.alibaba.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