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
