On Thu, Dec 25, 2014 at 05:43:28PM +0800, Hui Zhu wrote: > In [1], Joonsoo said that cma_alloc_counter is useless because pageblock > is isolated. > But if alloc_contig_range meet a busy range, it will undo_isolate_page_range > before goto try next range. At this time, __rmqueue_cma can begin allocd > CMA memory from the range.
Is there any real issue from this? When failed, we will quickly re-isolate pageblock for adjacent page so there is no big problem I guess. If there is real issue, how about doing start_isolation/undo_isolation in cma_alloc()? It would reduce useless do/undo isolation due to failed trial. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
