mm: free idle swap cache page after COW
Subsystems (3)
PATCH 1/1 mm: free idle swap cache page after COW
With commit 09854ba94c6a ("mm: do_wp_page() simplification"), after COW, the idle swap cache page (neither the page nor the corresponding swap entry is mapped by any process) will be left in the LRU list, even if it's in the active list or the head of the inactive list. So, the page reclaimer may take quite some overhead to reclaim these actually unused pages.
To help the page reclaiming, in this patch, after COW, the idle swap cache page will be tried to be freed. To avoid to introduce much overhead to the hot COW code path,
a) there's almost zero overhead for non-swap case via checking PageSwapCache() firstly.
b) the page lock is acquired via trylock only.
To test the patch, we used pmbench memory accessing benchmark with working-set larger than available memory on a 2-socket Intel server with a NVMe SSD as swap device. Test results shows that the pmbench score increases up to 23.8% with the decreased size of swap cache and swapin throughput.
--- include/linux/swap.h | 5 +++++ mm/memory.c | 2 ++ mm/swap_state.c | 2 +- 3 files changed, 8 insertions(+), 1 deletion(-)
include/linux/swap.h +5 -0
@@ -451,6 +451,7 @@ extern void __delete_from_swap_cache(struct page *page,extern void delete_from_swap_cache (struct page *);extern void clear_shadow_from_swap_cache (int type,unsigned long begin,unsigned long end); +extern void free_swap_cache (struct page *);extern void free_page_and_swap_cache (struct page *);extern void free_pages_and_swap_cache (struct page **,int ); extern struct page *lookup_swap_cache(swp_entry_t entry,
@@ -560,6 +561,10 @@ static inline struct address_space *swap_address_space(swp_entry_t entry)#define free_pages_and_swap_cache (pages, nr) \ release_pages((pages), (nr)); +static inline void free_swap_cache (struct page *page) +{ +} +static inline void show_swap_cache_info (void ) { }
mm/memory.c +2 -0
@@ -3104,6 +3104,8 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)munlock_vma_page (old_page);unlock_page (old_page); } +if (page_copied) +free_swap_cache (old_page);put_page (old_page); }return page_copied ?VM_FAULT_WRITE :0 ;
mm/swap_state.c +1 -1
@@ -285,7 +285,7 @@ void clear_shadow_from_swap_cache(int type, unsigned long begin,* try_to_free_swap() _with_ the lock. * - Marcelo */ -static inline void free_swap_cache (struct page *page) +void free_swap_cache (struct page *page) {if (PageSwapCache (page) && !page_mapped (page) &&trylock_page (page)) {try_to_free_swap (page);
Signature · 1 line
2.30.2
Quoted 14 lines · Huang Ying
With commit
09854ba94c6a("mm:do_wp_page()simplification"), after COW, the idle swap cache page (neither the page nor the corresponding swap entry is mapped by any process) will be left in the LRU list, even if it's in the active list or the head of the inactive list. So, the page reclaimer may take quite some overhead to reclaim these actually unused pages.To help the page reclaiming, in this patch, after COW, the idle swap cache page will be tried to be freed. To avoid to introduce much overhead to the hot COW code path,
a) there's almost zero overhead for non-swap case via checking
PageSwapCache()firstly.
Quoted 7 lines
b) the page lock is acquired via trylock only.
To test the patch, we used pmbench memory accessing benchmark with working-set larger than available memory on a 2-socket Intel server with a NVMe SSD as swap device. Test results shows that the pmbench score increases up to 23.8% with the decreased size of swap cache and swapin throughput.
So 2 percentage points better than my original idea? Sweet.
mm/memory.c static vm_fault_t wp_page_copy(struct vm_fault *vmf) · line 3111
Quoted 13 lines
mm/memory.c +2
-0@@ -3104,6 +3104,8 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)munlock_vma_page (old_page);unlock_page (old_page); } +if (page_copied) +free_swap_cache (old_page);put_page (old_page); }return page_copied ?VM_FAULT_WRITE :0 ;
Why not ...
if (page_copied) free_page_and_swap_cache(old_page); else put_page(old_page);
then you don't need to expose free_swap_cache(). Or does the test for huge_zero_page mess this up?
Quoted 41 lines · Matthew Wilcox
Quoted 14 lines · Huang Ying
With commit
09854ba94c6a("mm:do_wp_page()simplification"), after COW, the idle swap cache page (neither the page nor the corresponding swap entry is mapped by any process) will be left in the LRU list, even if it's in the active list or the head of the inactive list. So, the page reclaimer may take quite some overhead to reclaim these actually unused pages.To help the page reclaiming, in this patch, after COW, the idle swap cache page will be tried to be freed. To avoid to introduce much overhead to the hot COW code path,
a) there's almost zero overhead for non-swap case via checking
PageSwapCache()firstly.Quoted 7 lines
b) the page lock is acquired via trylock only.
To test the patch, we used pmbench memory accessing benchmark with working-set larger than available memory on a 2-socket Intel server with a NVMe SSD as swap device. Test results shows that the pmbench score increases up to 23.8% with the decreased size of swap cache and swapin throughput.
So 2 percentage points better than my original idea? Sweet.
mm/memory.c static vm_fault_t wp_page_copy(struct vm_fault *vmf) · line 3111
Quoted 13 lines
mm/memory.c +2
-0@@ -3104,6 +3104,8 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)munlock_vma_page (old_page);unlock_page (old_page); } +if (page_copied) +free_swap_cache (old_page);put_page (old_page); }return page_copied ?VM_FAULT_WRITE :0 ;Why not ...
Quoted 7 lines
if (page_copied) free_page_and_swap_cache(old_page); else put_page(old_page);then you don't need to expose
free_swap_cache(). Or does the test forhuge_zero_pagemess this up?
It's free_page[s]_and_swap_cache() we should reconsider, IMO.
free_swap_cache() makes for a clean API function that does one thing, and does it right. free_page_and_swap_cache() combines two independent operations, which has the habit of accumulating special case-handling for some callers that is unncessary overhead for others (Abstraction Inversion anti-pattern).
For example, free_page_and_swap_cache() adds an is_huge_zero_page() check around the put_page() for the tlb batching code. This isn't needed here. AFAICS it is also unnecessary for the other callsite, __collapse_huge_page_copy(), where context rules out zero pages.
The common put_page() in Huang's version also makes it slighly easier to follow the lifetime of old_page.
So I'd say exposing free_swap_cache() is a good move, for this patch and in general.
Quoted 8 lines · Johannes Weiner
It's free_page[s]_and_swap_cache() we should reconsider, IMO.
free_swap_cache()makes for a clean API function that does one thing, and does it right.free_page_and_swap_cache()combines two independent operations, which has the habit of accumulating special case-handling for some callers that is unncessary overhead for others (Abstraction Inversion anti-pattern).
Agreed. That "free_page_and_swap_cache()" function is odd. Much better written as
free_swap_cache();
free_page();because there's no real advantage to try to merge the two.
It's not like the merged function can actually do any optimization based on the merging, it just does the above anyway - except it then has that extra odd huge_zero_page test that makes no sense what-so-ever.
So if anything we should try to get rid of uses of that odd free_page_and_swap_cache() thing. But it's not exactly urgent.
Linus
Linus
Quoted 22 lines · Huang Ying
With commit
09854ba94c6a("mm:do_wp_page()simplification"), after COW, the idle swap cache page (neither the page nor the corresponding swap entry is mapped by any process) will be left in the LRU list, even if it's in the active list or the head of the inactive list. So, the page reclaimer may take quite some overhead to reclaim these actually unused pages.To help the page reclaiming, in this patch, after COW, the idle swap cache page will be tried to be freed. To avoid to introduce much overhead to the hot COW code path,
a) there's almost zero overhead for non-swap case via checking
PageSwapCache()firstly.b) the page lock is acquired via trylock only.
To test the patch, we used pmbench memory accessing benchmark with working-set larger than available memory on a 2-socket Intel server with a NVMe SSD as swap device. Test results shows that the pmbench score increases up to 23.8% with the decreased size of swap cache and swapin throughput.
Quoted 12 lines
Signed-off-by "Huang, Ying" <[email protected]>Cc Matthew Wilcox <[email protected]>Cc Linus Torvalds <[email protected]>Cc Peter Xu <[email protected]>Cc Hugh Dickins <[email protected]>Cc Mel Gorman <[email protected]>Cc Rik van Riel <[email protected]>Cc Andrea Arcangeli <[email protected]>Cc Michal Hocko <[email protected]>Cc Dave Hansen <[email protected]>Cc Tim Chen <[email protected]>