On Tue, Jun 7, 2016 at 11:55 PM, Laura Abbott wrote:
> You could try backporting the ZONE_CMA patches
> http://article.gmane.org/gmane.linux.kernel.mm/152016 . The primary problem
> there was CMA utilization but there was some discussion about migration
> success as well
On Tue, Jun 7, 2016 at 11:55 PM, Laura Abbott wrote:
> You could try backporting the ZONE_CMA patches
> http://article.gmane.org/gmane.linux.kernel.mm/152016 . The primary problem
> there was CMA utilization but there was some discussion about migration
> success as well
On 06/07/2016 05:59 AM, Shawn Guo wrote:
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
On 06/07/2016 05:59 AM, Shawn Guo wrote:
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
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
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
6 matches
Mail list logo