From: Xin Hao <xhao@linux.alibaba.com>
To: David Hildenbrand <david@redhat.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: Thu, 17 Mar 2022 15:03:11 +0800 [thread overview]
Message-ID: <6e6ef9fa-3916-3449-954d-efd63a959019@linux.alibaba.com> (raw)
In-Reply-To: <a1e0a9e9-07ef-8d1c-a409-2b4fb12ed553@redhat.com>
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.
>
--
Best Regards!
Xin Hao
next prev parent reply other threads:[~2022-03-17 7:03 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 [this message]
2022-03-17 16:42 ` David Hildenbrand
2022-03-18 5:13 ` xhao
2022-03-18 8:29 ` David Hildenbrand
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=6e6ef9fa-3916-3449-954d-efd63a959019@linux.alibaba.com \
--to=xhao@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongwei.wang@linux.alibaba.com \
--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