On 17.03.22 08:03, Xin Hao wrote:
Hi David,Hm, not quite. We can place movable allocations on cma areas, to be
On 3/16/22 11:09 PM, David Hildenbrand wrote:
On 15.03.22 17:37, Xin Hao wrote:Thanks, i will fix it.
s/minotor/monitor/
I may not be describing exactly what i mean,My intention is to find outThe purpose of these patches is to add CMA memory monitoring function.I'm sorry, but it's hard to figure out what the target use case should
In some memory tight scenarios, it will be a good choice to release more
memory by monitoring the CMA memory.
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?
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.
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.
--