On Wed, Sep 07, 2016 at 09:45:59AM -0700, Huang, Ying wrote:
> The advantages of the THP swap support include:
> - Batch the swap operations for the THP to reduce lock
> acquiring/releasing, including allocating/freeing the swap space,
> adding/deleting to/from the swap cache, and writing/reading the swap
> space, etc. This will help improve the performance of the THP swap.
> - The THP swap space read/write will be 2M sequential IO. It is
> particularly helpful for the swap read, which usually are 4k random
> IO. This will improve the performance of the THP swap too.
I think this is not a problem. Even with current early split, we are allocating
swap entry sequentially, after IO is dispatched, block layer will merge IO to
> - It will help the memory fragmentation, especially when the THP is
> heavily used by the applications. The 2M continuous pages will be
> free up after THP swapping out.
So this is impossible without THP swapin. While 2M swapout makes a lot of
sense, I doubt 2M swapin is really useful. What kind of application is
'optimized' to do sequential memory access?
One advantage of THP swapout is to reduce TLB flush. Eg, when we split 2m to 4k
pages, we set swap entry for the 4k pages since your patch already allocates
swap entry before the split, so we only do tlb flush once in the split. Without
the delay THP split, we do twice tlb flush (split and unmap of swapout). I
don't see this in the patches, do I misread the code?