Messages in this thread | | | Date | Tue, 7 Jun 2016 20:59:13 +0800 | From | Shawn Guo <> | Subject | CMA region absolutely for a particular device? |
| |
Hi,
I'm using a separate CMA region than the system default one for a particular device to avoid fragmentation. It does help. But under certain circumstance (memory shortage), it seems some of the pages in the region will be used by system. The really bad thing is that when a CMA allocation tries to move these occupied pages around, it just fails to do so with messages like "alloc_contig_range: ... PFNs busy". These pages thus become holes in a contiguous block and prevent the allocation from succeeding.
Is it possible to make a CMA absolutely for a particular device, and even system movable pages cannot use the memory? I can reserve a memory region from kernel and manage it with some custom and private interface for that particular device. But obviously, the standard dma-mapping API and established underneath CMA infrastructural is more desirable to use, right?
This is an arm64 device running on 4.1 kernel. Any comments or suggestions will be appreciated. Thanks.
Shawn
| |