David Rientjes <rientjes@xxxxxxxxxx> writes: > On Mon, 20 Mar 2017, Huang, Ying wrote: > >> From: Huang Ying <ying.huang@xxxxxxxxx> >> >> Now vzalloc() is used in swap code to allocate various data >> structures, such as swap cache, swap slots cache, cluster info, etc. >> Because the size may be too large on some system, so that normal >> kzalloc() may fail. But using kzalloc() has some advantages, for >> example, less memory fragmentation, less TLB pressure, etc. So change >> the data structure allocation in swap code to use kvzalloc() which >> will try kzalloc() firstly, and fallback to vzalloc() if kzalloc() >> failed. >> > > As questioned in -v1 of this patch, what is the benefit of directly > compacting and reclaiming memory for high-order pages by first preferring > kmalloc() if this does not require contiguous memory? The memory allocation here is only for swap on time, not for swap out/in time. The performance of swap on is not considered critical. But if the kmalloc() is used instead of the vmalloc(), the swap out/in performance could be improved (marginally). More importantly, the interference for the other activity on the system could be reduced, For example, less memory fragmentation, less TLB usage of swap subsystem, etc. Best Regards, Huang, Ying -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
