Re: drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy
From: Vlastimil Babka <hidden>
Date: 2016-12-02 06:36:55
Also in:
dri-devel, lkml
On 12/01/2016 10:02 PM, Michal Nazarewicz wrote:
On Thu, Dec 01 2016, Michal Hocko wrote:quoted
I am not familiar with this code so I cannot really argue but a quick look at rmem_cma_setup doesn't suggest any speicific placing or anything...early_cma parses a??cmaa?? command line argument which can specify where exactly the default CMA area is to be located. Furthermore, CMA areas can be assigned per-device (via the Device Tree IIRC).
OK, but the context of this bug report is a generic cma pool and generic dma alloc, which tries cma first and then fallback to alloc_pages_node(). If a device really requires specific placing as you suggest, then it probably uses a different allocation interface, otherwise there would be some flag to disallow the alloc_pages_node() fallback? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>