mm: fix some MADV_FREE issues
Subsystems (13)
v5 cover mm: fix some MADV_FREE issues
Hi,
We are trying to use MADV_FREE in jemalloc. Several issues are found. Without solving the issues, jemalloc can't use the MADV_FREE feature.
- Doesn't support system without swap enabled. Because if swap is off, we can't or can't efficiently age anonymous pages. And since MADV_FREE pages are mixed with other anonymous pages, we can't reclaim MADV_FREE pages. In current implementation, MADV_FREE will fallback to MADV_DONTNEED without swap enabled. But in our environment, a lot of machines don't enable swap. This will prevent our setup using MADV_FREE.
- Increases memory pressure. page reclaim bias file pages reclaim against anonymous pages. This doesn't make sense for MADV_FREE pages, because those pages could be freed easily and refilled with very slight penality. Even page reclaim doesn't bias file pages, there is still an issue, because MADV_FREE pages and other anonymous pages are mixed together. To reclaim a MADV_FREE page, we probably must scan a lot of other anonymous pages, which is inefficient. In our test, we usually see oom with MADV_FREE enabled and nothing without it.
- Accounting. There are two accounting problems. We don't have a global accounting. If the system is abnormal, we don't know if it's a problem from MADV_FREE side. The other problem is RSS accounting. MADV_FREE pages are accounted as normal anon pages and reclaimed lazily, so application's RSS becomes bigger. This confuses our workloads. We have monitoring daemon running and if it finds applications' RSS becomes abnormal, the daemon will kill the applications even kernel can reclaim the memory easily.
To address the first the two issues, we can either put MADV_FREE pages into a separate LRU list (Minchan's previous patches and V1 patches), or put them into LRU_INACTIVE_FILE list (suggested by Johannes). The patchset use the second idea. The reason is LRU_INACTIVE_FILE list is tiny nowadays and should be full of used once file pages. So we can still efficiently reclaim MADV_FREE pages there without interference with other anon and active file pages. Putting the pages into inactive file list also has an advantage which allows page reclaim to prioritize MADV_FREE pages and used once file pages. MADV_FREE pages are put into the lru list and clear SwapBacked flag, so PageAnon(page) && !PageSwapBacked(page) will indicate a MADV_FREE pages. These pages will directly freed without pageout if they are clean, otherwise normal swap will reclaim them.
For the third issue, the previous post adds global accounting and a separate RSS count for MADV_FREE pages. The problem is we never get accurate accounting for MADV_FREE pages. The pages are mapped to userspace, can be dirtied without notice from kernel side. To get accurate accounting, we could write protect the page, but then there is extra page fault overhead, which people don't want to pay. Jemalloc guys have concerns about the inaccurate accounting, so this post drops the accounting patches temporarily. The info exported to /proc/pid/smaps for MADV_FREE pages are kept, which is the only place we can get accurate accounting right now.
Thanks,
Shaohua
V4->V5:
- Fix some minor issues pointed out by Johannes
- Integrate Johannes's cleanup patch
- Fix a bug to avoid swapin page is dicarded silently
V3->V4:
- rebase to latest -mm tree
- Address several issues pointed out by Johannes and Minchan
- Dropped vmstat and RSS accounting
http://marc.info/?l=linux-mm&m=148778961127710&w=2
V2->V3:
- rebase to latest -mm tree
- Address severl issues pointed out by Minchan
- Add more descriptions
http://marc.info/?l=linux-mm&m=148710098701674&w=2
V1->V2:
- Put MADV_FREE pages into LRU_INACTIVE_FILE list instead of adding a new lru list, suggested by Johannes
- Add RSS support
http://marc.info/?l=linux-mm&m=148616481928054&w=2
Minchan previous patches:
http://marc.info/?l=linux-mm&m=144800657002763&w=2
----------------------
Shaohua Li (6):
mm: delete unnecessary TTU_* flags
mm: don't assume anonymous pages have SwapBacked flag
mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
mm: reclaim MADV_FREE pages
mm: enable MADV_FREE for swapless system
proc: show MADV_FREE pages info in smaps
Documentation/filesystems/proc.txt | 4 +++ fs/proc/task_mmu.c | 8 +++++- include/linux/rmap.h | 24 ++++++++---------- include/linux/swap.h | 2 +- include/linux/vm_event_item.h | 2 +- mm/huge_memory.c | 6 ++--- mm/khugepaged.c | 8 +++--- mm/madvise.c | 11 ++------- mm/memory-failure.c | 2 +- mm/migrate.c | 3 ++- mm/rmap.c | 43 +++++++++++++++----------------- mm/swap.c | 50 +++++++++++++++++++++----------------- mm/vmscan.c | 45 +++++++++++++++++++--------------- mm/vmstat.c | 1 + 14 files changed, 107 insertions(+), 102 deletions(-)
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 1/6 mm: delete unnecessary TTU_* flags
Johannes pointed out TTU_LZFREE is unnecessary. It's true because we always have the flag set if we want to do an unmap. For cases we don't do an unmap, the TTU_LZFREE part of code should never run.
Also the TTU_UNMAP is unnecessary. If no other flags set (for example, TTU_MIGRATION), an unmap is implied.
The patch includes Johannes's cleanup and dead TTU_ACTION macro removal code
--- include/linux/rmap.h | 22 +++++++++------------- mm/memory-failure.c | 2 +- mm/rmap.c | 2 +- mm/vmscan.c | 11 ++++------- 4 files changed, 15 insertions(+), 22 deletions(-)
include/linux/rmap.h +9 -13
@@ -83,19 +83,17 @@ struct anon_vma_chain { };enum ttu_flags { -TTU_UNMAP =1 ,/* unmap mode */ -TTU_MIGRATION =2 ,/* migration mode */ -TTU_MUNLOCK =4 ,/* munlock mode */ -TTU_LZFREE =8 ,/* lazy free mode */ -TTU_SPLIT_HUGE_PMD =16 ,/* split huge PMD if any */ - -TTU_IGNORE_MLOCK = (1 <<8 ),/* ignore mlock */ -TTU_IGNORE_ACCESS = (1 <<9 ),/* don't age */ -TTU_IGNORE_HWPOISON = (1 <<10 ),/* corrupted page is recoverable */ -TTU_BATCH_FLUSH = (1 <<11 ),/* Batch TLB flushes where possible +TTU_MIGRATION =0x1 ,/* migration mode */ +TTU_MUNLOCK =0x2 ,/* munlock mode */ + +TTU_SPLIT_HUGE_PMD =0x4 ,/* split huge PMD if any */ +TTU_IGNORE_MLOCK =0x8 ,/* ignore mlock */ +TTU_IGNORE_ACCESS =0x10 ,/* don't age */ +TTU_IGNORE_HWPOISON =0x20 ,/* corrupted page is recoverable */ +TTU_BATCH_FLUSH =0x40 ,/* Batch TLB flushes where possible * and caller guarantees they will * do a final flush if necessary */ -TTU_RMAP_LOCKED = (1 <<12 )/* do not grab rmap lock: +TTU_RMAP_LOCKED =0x80 /* do not grab rmap lock: * caller holds it */ };
@@ -193,8 +191,6 @@ static inline void page_dup_rmap(struct page *page, bool compound)int page_referenced (struct page *,int is_locked,struct mem_cgroup *memcg,unsigned long *vm_flags); -#define TTU_ACTION (x) ((x) & TTU_ACTION_MASK) -int try_to_unmap (struct page *,enum ttu_flags flags);/* Avoid racy checks */
mm/memory-failure.c +1 -1
@@ -906,7 +906,7 @@ EXPORT_SYMBOL_GPL(get_hwpoison_page);static int hwpoison_user_mappings (struct page *p,unsigned long pfn,int trapno,int flags,struct page **hpagep) { -enum ttu_flags ttu =TTU_UNMAP |TTU_IGNORE_MLOCK |TTU_IGNORE_ACCESS ; +enum ttu_flags ttu =TTU_IGNORE_MLOCK |TTU_IGNORE_ACCESS ;struct address_space *mapping;LIST_HEAD (tokill);int ret;
mm/rmap.c +1 -1
@@ -1418,7 +1418,7 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,*/ VM_BUG_ON_PAGE (!PageSwapCache (page), page); -if (!PageDirty (page) && (flags &TTU_LZFREE )) { +if (!PageDirty (page)) {/* It's a freeable page by MADV_FREE */ dec_mm_counter (mm,MM_ANONPAGES ); rp->lazyfreed++;
mm/vmscan.c +4 -7
@@ -971,7 +971,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,int may_enter_fs;enum page_references references =PAGEREF_RECLAIM_CLEAN ;bool dirty, writeback; -bool lazyfree = false;int ret =SWAP_SUCCESS ;cond_resched ();
@@ -1125,7 +1124,6 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;if (!add_to_swap (page, page_list)) goto activate_locked; - lazyfree = true; may_enter_fs =1 ;/* Adding to swap updated mapping */
@@ -1143,9 +1141,8 @@ static unsigned long shrink_page_list(struct list_head *page_list,* processes. Try to unmap it here. */ if (page_mapped (page) && mapping) { -switch (ret =try_to_unmap (page, lazyfree ? - (ttu_flags |TTU_BATCH_FLUSH |TTU_LZFREE ) : - (ttu_flags |TTU_BATCH_FLUSH ))) { +switch (ret =try_to_unmap (page, + ttu_flags |TTU_BATCH_FLUSH )) {case SWAP_FAIL : nr_unmap_fail++; goto activate_locked;
@@ -1353,7 +1350,7 @@ unsigned long reclaim_clean_pages_from_list(struct zone *zone, } ret =shrink_page_list (&clean_pages, zone->zone_pgdat, &sc, -TTU_UNMAP |TTU_IGNORE_ACCESS ,NULL , true); +TTU_IGNORE_ACCESS ,NULL , true);list_splice (&clean_pages, page_list);mod_node_page_state (zone->zone_pgdat,NR_ISOLATED_FILE , -ret);return ret;
@@ -1760,7 +1757,7 @@ shrink_inactive_list(unsigned long nr_to_scan, struct lruvec *lruvec,if (nr_taken ==0 )return 0 ; - nr_reclaimed =shrink_page_list (&page_list, pgdat, sc,TTU_UNMAP , + nr_reclaimed =shrink_page_list (&page_list, pgdat, sc,0 , &stat, false);spin_lock_irq (&pgdat->lru_lock);
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 1/6] mm: delete unnecessary TTU_* flags
Quoted 10 lines · Shaohua Li
Johannes pointed out
TTU_LZFREEis unnecessary. It's true because we always have the flag set if we want to do an unmap. For cases we don't do an unmap, theTTU_LZFREEpart of code should never run.Also the
TTU_UNMAPis unnecessary. If no other flags set (for example,TTU_MIGRATION), an unmap is implied.The patch includes Johannes's cleanup and dead
TTU_ACTIONmacro removal code
Quoted 10 lines
Cc Michal Hocko <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Acked-by Johannes Weiner <[email protected]>Acked-by Minchan Kim <[email protected]>Acked-by Hillf Danton <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 128 lines
--- include/linux/rmap.h | 22 +++++++++------------- mm/memory-failure.c | 2 +- mm/rmap.c | 2 +- mm/vmscan.c | 11 ++++------- 4 files changed, 15 insertions(+), 22 deletions(-)include/linux/rmap.h +9
-13@@ -83,19 +83,17 @@ struct anon_vma_chain { };enum ttu_flags { -TTU_UNMAP =1 ,/* unmap mode */ -TTU_MIGRATION =2 ,/* migration mode */ -TTU_MUNLOCK =4 ,/* munlock mode */ -TTU_LZFREE =8 ,/* lazy free mode */ -TTU_SPLIT_HUGE_PMD =16 ,/* split huge PMD if any */ - -TTU_IGNORE_MLOCK = (1 <<8 ),/* ignore mlock */ -TTU_IGNORE_ACCESS = (1 <<9 ),/* don't age */ -TTU_IGNORE_HWPOISON = (1 <<10 ),/* corrupted page is recoverable */ -TTU_BATCH_FLUSH = (1 <<11 ),/* Batch TLB flushes where possible +TTU_MIGRATION =0x1 ,/* migration mode */ +TTU_MUNLOCK =0x2 ,/* munlock mode */ + +TTU_SPLIT_HUGE_PMD =0x4 ,/* split huge PMD if any */ +TTU_IGNORE_MLOCK =0x8 ,/* ignore mlock */ +TTU_IGNORE_ACCESS =0x10 ,/* don't age */ +TTU_IGNORE_HWPOISON =0x20 ,/* corrupted page is recoverable */ +TTU_BATCH_FLUSH =0x40 ,/* Batch TLB flushes where possible * and caller guarantees they will * do a final flush if necessary */ -TTU_RMAP_LOCKED = (1 <<12 )/* do not grab rmap lock: +TTU_RMAP_LOCKED =0x80 /* do not grab rmap lock: * caller holds it */ };@@ -193,8 +191,6 @@ static inline void page_dup_rmap(struct page *page, bool compound)int page_referenced (struct page *,int is_locked,struct mem_cgroup *memcg,unsigned long *vm_flags); -#define TTU_ACTION (x) ((x) & TTU_ACTION_MASK) -int try_to_unmap (struct page *,enum ttu_flags flags);/* Avoid racy checks */ mm/memory-failure.c +1
-1@@ -906,7 +906,7 @@ EXPORT_SYMBOL_GPL(get_hwpoison_page);static int hwpoison_user_mappings (struct page *p,unsigned long pfn,int trapno,int flags,struct page **hpagep) { -enum ttu_flags ttu =TTU_UNMAP |TTU_IGNORE_MLOCK |TTU_IGNORE_ACCESS ; +enum ttu_flags ttu =TTU_IGNORE_MLOCK |TTU_IGNORE_ACCESS ;struct address_space *mapping;LIST_HEAD (tokill);int ret;mm/rmap.c +1
-1@@ -1418,7 +1418,7 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,*/ VM_BUG_ON_PAGE (!PageSwapCache (page), page); -if (!PageDirty (page) && (flags &TTU_LZFREE )) { +if (!PageDirty (page)) {/* It's a freeable page by MADV_FREE */ dec_mm_counter (mm,MM_ANONPAGES ); rp->lazyfreed++;mm/vmscan.c +4
-7@@ -971,7 +971,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,int may_enter_fs;enum page_references references =PAGEREF_RECLAIM_CLEAN ;bool dirty, writeback; -bool lazyfree = false;int ret =SWAP_SUCCESS ;cond_resched ();@@ -1125,7 +1124,6 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;if (!add_to_swap (page, page_list)) goto activate_locked; - lazyfree = true; may_enter_fs =1 ;/* Adding to swap updated mapping */ @@ -1143,9 +1141,8 @@ static unsigned long shrink_page_list(struct list_head *page_list,* processes. Try to unmap it here. */ if (page_mapped (page) && mapping) { -switch (ret =try_to_unmap (page, lazyfree ? - (ttu_flags |TTU_BATCH_FLUSH |TTU_LZFREE ) : - (ttu_flags |TTU_BATCH_FLUSH ))) { +switch (ret =try_to_unmap (page, + ttu_flags |TTU_BATCH_FLUSH )) {case SWAP_FAIL : nr_unmap_fail++; goto activate_locked;@@ -1353,7 +1350,7 @@ unsigned long reclaim_clean_pages_from_list(struct zone *zone, } ret =shrink_page_list (&clean_pages, zone->zone_pgdat, &sc, -TTU_UNMAP |TTU_IGNORE_ACCESS ,NULL , true); +TTU_IGNORE_ACCESS ,NULL , true);list_splice (&clean_pages, page_list);mod_node_page_state (zone->zone_pgdat,NR_ISOLATED_FILE , -ret);return ret;@@ -1760,7 +1757,7 @@ shrink_inactive_list(unsigned long nr_to_scan, struct lruvec *lruvec,if (nr_taken ==0 )return 0 ; - nr_reclaimed =shrink_page_list (&page_list, pgdat, sc,TTU_UNMAP , + nr_reclaimed =shrink_page_list (&page_list, pgdat, sc,0 , &stat, false);spin_lock_irq (&pgdat->lru_lock);Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 2/6 mm: don't assume anonymous pages have SwapBacked flag
In reply to Shaohua LiThere are a few places the code assumes anonymous pages should have SwapBacked flag set. MADV_FREE pages are anonymous pages but we are going to add them to LRU_INACTIVE_FILE list and clear SwapBacked flag for them. The assumption doesn't hold any more, so fix them.
--- mm/huge_memory.c | 1 - mm/khugepaged.c | 8 +++----- mm/migrate.c | 3 ++- mm/rmap.c | 3 ++- 4 files changed, 7 insertions(+), 8 deletions(-)
mm/huge_memory.c +0 -1
@@ -2361,7 +2361,6 @@ int split_huge_page_to_list(struct page *page, struct list_head *list)VM_BUG_ON_PAGE (is_huge_zero_page (page), page);VM_BUG_ON_PAGE (!PageLocked (page), page); -VM_BUG_ON_PAGE (!PageSwapBacked (page), page);VM_BUG_ON_PAGE (!PageCompound (page), page);if (PageAnon (head)) {
mm/khugepaged.c +3 -5
@@ -481,8 +481,7 @@ void __khugepaged_exit(struct mm_struct *mm)static void release_pte_page (struct page *page) { -/* 0 stands for page_is_file_cache(page) == false */ -dec_node_page_state (page,NR_ISOLATED_ANON +0 ); +dec_node_page_state (page,NR_ISOLATED_ANON +page_is_file_cache (page));unlock_page (page);putback_lru_page (page); }
@@ -530,7 +529,6 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma,VM_BUG_ON_PAGE (PageCompound (page), page);VM_BUG_ON_PAGE (!PageAnon (page), page); -VM_BUG_ON_PAGE (!PageSwapBacked (page), page);/* * We can do it before isolate_lru_page because the
@@ -577,8 +575,8 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma, result =SCAN_DEL_PAGE_LRU ; goto out; } -/* 0 stands for page_is_file_cache(page) == false */ -inc_node_page_state (page,NR_ISOLATED_ANON +0 ); +inc_node_page_state (page, +NR_ISOLATED_ANON +page_is_file_cache (page));VM_BUG_ON_PAGE (!PageLocked (page), page);VM_BUG_ON_PAGE (PageLRU (page), page);
mm/migrate.c +2 -1
@@ -1943,7 +1943,8 @@ int migrate_misplaced_transhuge_page(struct mm_struct *mm,/* Prepare a page as a migration target */ __SetPageLocked (new_page); -__SetPageSwapBacked (new_page); +if (PageSwapBacked (page)) +__SetPageSwapBacked (new_page);/* anon mapping, we can simply copy page->mapping to the new page: */ new_page->mapping = page->mapping;
mm/rmap.c +2 -1
@@ -1416,7 +1416,8 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,* Store the swap location in the pte. * See handle_pte_fault() ... */ -VM_BUG_ON_PAGE (!PageSwapCache (page), page); +VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), + page);if (!PageDirty (page)) {/* It's a freeable page by MADV_FREE */
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag
Quoted 14 lines · Shaohua Li
There are a few places the code assumes anonymous pages should have SwapBacked flag set.
MADV_FREEpages are anonymous pages but we are going to add them toLRU_INACTIVE_FILElist and clear SwapBacked flag for them. The assumption doesn't hold any more, so fix them.Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 1 line
---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag
In reply to Shaohua LiQuoted 5 lines · Shaohua Li
There are a few places the code assumes anonymous pages should have SwapBacked flag set.
MADV_FREEpages are anonymous pages but we are going to add them toLRU_INACTIVE_FILElist and clear SwapBacked flag for them. The assumption doesn't hold any more, so fix them.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Looks good to me.
[...]
mm/rmap.c static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma, · line 1420
Quoted 10 lines
index 96eb85c..c621088 100644
mm/rmap.c +2
-1@@ -1416,7 +1416,8 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,* Store the swap location in the pte. * See handle_pte_fault() ... */ -VM_BUG_ON_PAGE (!PageSwapCache (page), page); +VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), + page);
just this part makes me scratch my head. I really do not understand what kind of problem it tries to prevent from, maybe I am missing something obvoious...
Quoted 6 lines
mm/rmap.c +0
-0if (!PageDirty (page)) {/* It's a freeable page by MADV_FREE */ Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag
Quoted 17 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
There are a few places the code assumes anonymous pages should have SwapBacked flag set.
MADV_FREEpages are anonymous pages but we are going to add them toLRU_INACTIVE_FILElist and clear SwapBacked flag for them. The assumption doesn't hold any more, so fix them.Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>Looks good to me.
[...]
Quoted 14 lines
mm/rmap.c static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma, · line 1420
Quoted 10 lines
index 96eb85c..c621088 100644
mm/rmap.c +2
-1@@ -1416,7 +1416,8 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,* Store the swap location in the pte. * See handle_pte_fault() ... */ -VM_BUG_ON_PAGE (!PageSwapCache (page), page); +VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), + page);just this part makes me scratch my head. I really do not understand what kind of problem it tries to prevent from, maybe I am missing something obvoious...
Just check a page which isn't lazyfree but wrongly enters here without swap entry. Or maybe you suggest we delete this statement?
Thanks,
Shaohua
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag
Quoted 7 lines · Shaohua Li
Quoted 6 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
There are a few places the code assumes anonymous pages should have SwapBacked flag set.
MADV_FREEpages are anonymous pages but we are going to add them toLRU_INACTIVE_FILElist and clear SwapBacked flag for them. The assumption doesn't hold any more, so fix them.
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Anyway, feel free to add
Quoted 18 lines
Quoted 17 lines
Looks good to me.
[...]mm/rmap.c static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma, · line 1420
Quoted 10 lines
index 96eb85c..c621088 100644
mm/rmap.c +2
-1@@ -1416,7 +1416,8 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,* Store the swap location in the pte. * See handle_pte_fault() ... */ -VM_BUG_ON_PAGE (!PageSwapCache (page), page); +VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), + page);just this part makes me scratch my head. I really do not understand what kind of problem it tries to prevent from, maybe I am missing something obvoious...
Quoted 2 lines
Just check a page which isn't lazyfree but wrongly enters here without swap entry. Or maybe you suggest we delete this statement?
Ohh, I figured out when seeing later patch in the series, I then wanted to get back to this one but forgot... This on its own didn't really tell me much. Maybe a comment would be helpful or even drop the VM_BUG_ON altogether.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 3/6 mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
In reply to Shaohua Limadv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREE pages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaiming MADV_FREE pages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.
To speed up MADV_FREE pages reclaim, we put the pages into LRU_INACTIVE_FILE list. The rationale is LRU_INACTIVE_FILE list is tiny nowadays and should be full of used once file pages. Reclaiming MADV_FREE pages will not have much interfere of anonymous and active file pages. And the inactive file pages and MADV_FREE pages will be reclaimed according to their age, so we don't reclaim too many MADV_FREE pages too. Putting the MADV_FREE pages into LRU_INACTIVE_FILE_LIST also means we can reclaim the pages without swap support. This idea is suggested by Johannes.
This patch doesn't move MADV_FREE pages to LRU_INACTIVE_FILE list yet to avoid bisect failure, next patch will do it.
The patch is based on Minchan's original patch.
--- include/linux/swap.h | 2 +- include/linux/vm_event_item.h | 2 +- mm/huge_memory.c | 3 --- mm/madvise.c | 2 -- mm/swap.c | 50 ++++++++++++++++++++++++------------------- mm/vmstat.c | 1 + 6 files changed, 31 insertions(+), 29 deletions(-)
include/linux/swap.h +1 -1
@@ -279,7 +279,7 @@ extern void lru_add_drain_cpu(int cpu);extern void lru_add_drain_all (void );extern void rotate_reclaimable_page (struct page *page);extern void deactivate_file_page (struct page *page); -extern void deactivate_page (struct page *page); +extern void mark_page_lazyfree (struct page *page);extern void swap_setup (void );extern void add_page_to_unevictable_list (struct page *page);
include/linux/vm_event_item.h +1 -1
@@ -25,7 +25,7 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,FOR_ALL_ZONES (PGALLOC ),FOR_ALL_ZONES (ALLOCSTALL ),FOR_ALL_ZONES (PGSCAN_SKIP ), -PGFREE ,PGACTIVATE ,PGDEACTIVATE , +PGFREE ,PGACTIVATE ,PGDEACTIVATE ,PGLAZYFREE ,PGFAULT ,PGMAJFAULT ,PGLAZYFREED , PGREFILL,
mm/huge_memory.c +0 -3
@@ -1562,9 +1562,6 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma,ClearPageDirty (page);unlock_page (page); -if (PageActive (page)) -deactivate_page (page); -if (pmd_young (orig_pmd) ||pmd_dirty (orig_pmd)) { orig_pmd =pmdp_huge_get_and_clear_full (tlb->mm, addr, pmd, tlb->fullmm);
mm/madvise.c +0 -2
@@ -411,8 +411,6 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr, ptent =pte_mkold (ptent); ptent =pte_mkclean (ptent);set_pte_at (mm, addr, pte, ptent); -if (PageActive (page)) -deactivate_page (page);tlb_remove_tlb_entry (tlb, pte, addr); } }
mm/swap.c +28 -22
93 lines not on this page · raw message
mm/vmstat.c +1 -0
@@ -992,6 +992,7 @@ const char * const vmstat_text[] = {"pgfree" ,"pgactivate" ,"pgdeactivate" , +"pglazyfree" ,"pgfault" , "pgmajfault",
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
Hello Shaohua,
Quoted 25 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.The patch is based on Minchan's original patch.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
This patch doesn't address I pointed out in v4.
https://marc.info/?i=20170224233752.GB4635%40bbox
Let's discuss it if you still are against.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
Quoted 37 lines · Minchan Kim
Hello Shaohua,
Quoted 25 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.The patch is based on Minchan's original patch.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 5 lines
This patch doesn't address I pointed out in v4.
https://marc.info/?i=20170224233752.GB4635%40bbox
Let's discuss it if you still are against.
I really think a spearate patch makes the code clearer. There are a lot of places we introduce a function but don't use it immediately, if the way makes the code clearer. But anyway, I'll let Andrew decide if the two patches should be merged.
Thanks,
Shaohua
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
Quoted 1 line · Shaohua Li
On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote:
[...]
Quoted 10 lines
Quoted 5 lines
This patch doesn't address I pointed out in v4.
https://marc.info/?i=20170224233752.GB4635%40bbox
Let's discuss it if you still are against.
I really think a spearate patch makes the code clearer. There are a lot of places we introduce a function but don't use it immediately, if the way makes the code clearer. But anyway, I'll let Andrew decide if the two patches should be merged.
I agree that it is almost always _preferable_ to add new functions along with their callers. In this particular case I would lean towards keeping the separation the way Shaohua did it because it makes the code really cleaner IMHO.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Minchan Kim
Acked-byRe: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
In reply to Shaohua LiHi,
Quoted 40 lines · Shaohua Li
Quoted 39 lines · Minchan Kim
Hello Shaohua,
Quoted 25 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.The patch is based on Minchan's original patch.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>This patch doesn't address I pointed out in v4.
Quoted 8 lines
Quoted 3 lines
https://marc.info/?i=20170224233752.GB4635%40bbox
Let's discuss it if you still are against.
I really think a spearate patch makes the code clearer. There are a lot of places we introduce a function but don't use it immediately, if the way makes the code clearer. But anyway, I'll let Andrew decide if the two patches should be merged.
Okay, I don't insist it any more if others are happy but please keep it in mind that it's not a good habit, IMHO. Because
First of all, it makes review hard.
You introduce PGLAZYFREE in the patch but reviewer cannot find where it is used so cannot review the accouting is right.
You introduce mark_page_lazyfree in the patch but there is no callsite to use it. How can reviewer review it rightly? We cannot see what checks are missing in there and what checks are redundant, and what kinds of lock we need. It's hot path or slow path? Depending on it, we need to think approach.
There are many questions in there. It means we cannot review it without relying upon upcoming patches, which is really not helpful for the review.
As well, it adds unncessary bisect point which is not a good, either.
I really want to merge two patches(introduce part and use-it part) unless it makes review really hard or need per-subsystem apply.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
In reply to Shaohua LiQuoted 20 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.
Quoted 2 lines
This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.
This patch also changes behavior of madv_freed pages on the active list because they are not moved to the inactive list but considering how anon pages are reclaimed these days I do not really think this will be noticeable.
Quoted 10 lines
The patch is based on Minchan's original patch.
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 179 lines
--- include/linux/swap.h | 2 +- include/linux/vm_event_item.h | 2 +- mm/huge_memory.c | 3 --- mm/madvise.c | 2 -- mm/swap.c | 50 ++++++++++++++++++++++++------------------- mm/vmstat.c | 1 + 6 files changed, 31 insertions(+), 29 deletions(-)include/linux/swap.h +1
-1@@ -279,7 +279,7 @@ extern void lru_add_drain_cpu(int cpu);extern void lru_add_drain_all (void );extern void rotate_reclaimable_page (struct page *page);extern void deactivate_file_page (struct page *page); -extern void deactivate_page (struct page *page); +extern void mark_page_lazyfree (struct page *page);extern void swap_setup (void );extern void add_page_to_unevictable_list (struct page *page);include/linux/vm_event_item.h +1
-1@@ -25,7 +25,7 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,FOR_ALL_ZONES (PGALLOC ),FOR_ALL_ZONES (ALLOCSTALL ),FOR_ALL_ZONES (PGSCAN_SKIP ), -PGFREE ,PGACTIVATE ,PGDEACTIVATE , +PGFREE ,PGACTIVATE ,PGDEACTIVATE ,PGLAZYFREE ,PGFAULT ,PGMAJFAULT ,PGLAZYFREED , PGREFILL,mm/huge_memory.c +0
-3@@ -1562,9 +1562,6 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma,ClearPageDirty (page);unlock_page (page); -if (PageActive (page)) -deactivate_page (page); -if (pmd_young (orig_pmd) ||pmd_dirty (orig_pmd)) { orig_pmd =pmdp_huge_get_and_clear_full (tlb->mm, addr, pmd, tlb->fullmm);mm/madvise.c +0
-2@@ -411,8 +411,6 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr, ptent =pte_mkold (ptent); ptent =pte_mkclean (ptent);set_pte_at (mm, addr, pte, ptent); -if (PageActive (page)) -deactivate_page (page);tlb_remove_tlb_entry (tlb, pte, addr); } }mm/swap.c +28
-22@@ -46,7 +46,7 @@ int page_cluster; static DEFINE_PER_CPU(struct pagevec, lru_add_pvec); static DEFINE_PER_CPU(struct pagevec, lru_rotate_pvecs); static DEFINE_PER_CPU(struct pagevec, lru_deactivate_file_pvecs); -static DEFINE_PER_CPU(struct pagevec, lru_deactivate_pvecs); +static DEFINE_PER_CPU(struct pagevec, lru_lazyfree_pvecs);#ifdef CONFIG_SMP static DEFINE_PER_CPU(struct pagevec, activate_page_pvecs);#endif @@ -561,20 +561,26 @@ static void lru_deactivate_file_fn(struct page *page, struct lruvec *lruvec, } -static void lru_deactivate_fn (struct page *page,struct lruvec *lruvec, +static void lru_lazyfree_fn (struct page *page,struct lruvec *lruvec,void *arg) { -if (PageLRU (page) &&PageActive (page) && !PageUnevictable (page)) { -int file =page_is_file_cache (page); -int lru =page_lru_base_type (page); +if (PageLRU (page) &&PageAnon (page) &&PageSwapBacked (page) && + !PageUnevictable (page)) { +bool active =PageActive (page); -del_page_from_lru_list (page, lruvec, lru +LRU_ACTIVE ); +del_page_from_lru_list (page, lruvec,LRU_INACTIVE_ANON + active);ClearPageActive (page);ClearPageReferenced (page); -add_page_to_lru_list (page, lruvec, lru); +/* +* lazyfree pages are clean anonymous pages. They have +* SwapBacked flag cleared to distinguish normal anonymous +* pages +*/ +ClearPageSwapBacked (page); +add_page_to_lru_list (page, lruvec,LRU_INACTIVE_FILE ); -__count_vm_event (PGDEACTIVATE ); -update_page_reclaim_stat (lruvec, file,0 ); +__count_vm_events (PGLAZYFREE ,hpage_nr_pages (page)); +update_page_reclaim_stat (lruvec,1 ,0 ); } }@@ -604,9 +610,9 @@ void lru_add_drain_cpu(int cpu)if (pagevec_count (pvec))pagevec_lru_move_fn (pvec, lru_deactivate_file_fn,NULL ); - pvec = &per_cpu (lru_deactivate_pvecs, cpu); + pvec = &per_cpu (lru_lazyfree_pvecs, cpu);if (pagevec_count (pvec)) -pagevec_lru_move_fn (pvec, lru_deactivate_fn,NULL ); +pagevec_lru_move_fn (pvec, lru_lazyfree_fn,NULL );activate_page_drain (cpu); }@@ -638,22 +644,22 @@ void deactivate_file_page(struct page *page) }/** -* deactivate_page - deactivate a page +* mark_page_lazyfree - make an anon page lazyfree * @page: page to deactivate * -* deactivate_page() moves @page to the inactive list if @page was on the active -* list and was not an unevictable page. This is done to accelerate the reclaim -* of @page. +* mark_page_lazyfree() moves @page to the inactive file list. +* This is done to accelerate the reclaim of @page. */ -void deactivate_page (struct page *page) -{ -if (PageLRU (page) &&PageActive (page) && !PageUnevictable (page)) { -struct pagevec *pvec = &get_cpu_var (lru_deactivate_pvecs); +void mark_page_lazyfree (struct page *page) + { +if (PageLRU (page) &&PageAnon (page) &&PageSwapBacked (page) && + !PageUnevictable (page)) { +struct pagevec *pvec = &get_cpu_var (lru_lazyfree_pvecs);get_page (page);if (!pagevec_add (pvec, page) ||PageCompound (page)) -pagevec_lru_move_fn (pvec, lru_deactivate_fn,NULL ); -put_cpu_var (lru_deactivate_pvecs); +pagevec_lru_move_fn (pvec, lru_lazyfree_fn,NULL ); +put_cpu_var (lru_lazyfree_pvecs); } }@@ -704,7 +710,7 @@ void lru_add_drain_all(void)if (pagevec_count (&per_cpu (lru_add_pvec, cpu)) ||pagevec_count (&per_cpu (lru_rotate_pvecs, cpu)) ||pagevec_count (&per_cpu (lru_deactivate_file_pvecs, cpu)) || -pagevec_count (&per_cpu (lru_deactivate_pvecs, cpu)) || +pagevec_count (&per_cpu (lru_lazyfree_pvecs, cpu)) ||need_activate_page_drain (cpu)) {INIT_WORK (work, lru_add_drain_per_cpu);queue_work_on (cpu, lru_add_drain_wq, work);mm/vmstat.c +1
-0@@ -992,6 +992,7 @@ const char * const vmstat_text[] = {"pgfree" ,"pgactivate" ,"pgdeactivate" , +"pglazyfree" ,"pgfault" , "pgmajfault",Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
In reply to Shaohua LiQuoted 25 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.The patch is based on Minchan's original patch.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list
In reply to Shaohua LiQuoted 34 lines · Shaohua Li
madv
MADV_FREEindicate pages are 'lazyfree'. They are still anonymous pages, but they can be freed without pageout. To destinguish them against normal anonymous pages, we clear their SwapBacked flag.
MADV_FREEpages could be freed without pageout, so they pretty much like used once file pages. For such pages, we'd like to reclaim them once there is memory pressure. Also it might be unfair reclaimingMADV_FREEpages always before used once file pages and we definitively want to reclaim the pages before other anonymous and file pages.To speed up
MADV_FREEpages reclaim, we put the pages intoLRU_INACTIVE_FILElist. The rationale isLRU_INACTIVE_FILElist is tiny nowadays and should be full of used once file pages. ReclaimingMADV_FREEpages will not have much interfere of anonymous and active file pages. And the inactive file pages andMADV_FREEpages will be reclaimed according to their age, so we don't reclaim too manyMADV_FREEpages too. Putting theMADV_FREEpages intoLRU_INACTIVE_FILE_LISTalso means we can reclaim the pages without swap support. This idea is suggested by Johannes.This patch doesn't move
MADV_FREEpages toLRU_INACTIVE_FILElist yet to avoid bisect failure, next patch will do it.The patch is based on Minchan's original patch.
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Suggested-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 1 line
---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 4/6 mm: reclaim MADV_FREE pages
In reply to Shaohua LiWhen memory pressure is high, we free MADV_FREE pages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.
We use normal page reclaim policy. Since MADV_FREE pages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too many MADV_FREE pages before used once pages.
Based on Minchan's original patch
--- include/linux/rmap.h | 2 +- mm/huge_memory.c | 2 ++ mm/madvise.c | 1 + mm/rmap.c | 40 +++++++++++++++++----------------------- mm/vmscan.c | 34 ++++++++++++++++++++++------------ 5 files changed, 43 insertions(+), 36 deletions(-)
include/linux/rmap.h +1 -1
@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4#endif /* _LINUX_RMAP_H */
mm/huge_memory.c +2 -0
@@ -1571,6 +1571,8 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma,set_pmd_at (mm, addr, pmd, orig_pmd);tlb_remove_pmd_tlb_entry (tlb, pmd, addr); } + +mark_page_lazyfree (page); ret = true; out:spin_unlock (ptl);
mm/madvise.c +1 -0
@@ -413,6 +413,7 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,set_pte_at (mm, addr, pte, ptent);tlb_remove_tlb_entry (tlb, pte, addr); } +mark_page_lazyfree (page); } out:if (nr_swap) {
mm/rmap.c +17 -23
@@ -1281,11 +1281,6 @@ void page_remove_rmap(struct page *page, bool compound)*/ } -struct rmap_private { -enum ttu_flags flags; -int lazyfreed; -}; -/* * @arg: enum ttu_flags will be passed to this argument */
@@ -1301,8 +1296,7 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,pte_t pteval;struct page *subpage;int ret =SWAP_AGAIN ; -struct rmap_private *rp = arg; -enum ttu_flags flags = rp->flags; +enum ttu_flags flags = (enum ttu_flags )arg;/* munlock has nothing to gain from examining un-locked vmas */ if ((flags &TTU_MUNLOCK ) && !(vma->vm_flags &VM_LOCKED ))
@@ -1419,11 +1413,21 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), page); -if (!PageDirty (page)) { +/* +* swapin page could be clean, it has data stored in +* swap. We can't silently discard it without setting +* swap entry in the page table. +*/ +if (!PageDirty (page) && !PageSwapCache (page)) {/* It's a freeable page by MADV_FREE */ dec_mm_counter (mm,MM_ANONPAGES ); - rp->lazyfreed++; goto discard; + }else if (!PageSwapBacked (page)) { +/* dirty MADV_FREE page */ +set_pte_at (mm, address, pvmw.pte, pteval); + ret =SWAP_DIRTY ; +page_vma_mapped_walk_done (&pvmw); +break ; }if (swap_duplicate (entry) <0 ) {
@@ -1491,18 +1495,15 @@ static int page_mapcount_is_zero(struct page *page)* SWAP_AGAIN - we missed a mapping, try again later * SWAP_FAIL - the page is unswappable * SWAP_MLOCK - page is mlocked. +* SWAP_DIRTY - page is dirty MADV_FREE page */ int try_to_unmap (struct page *page,enum ttu_flags flags) {int ret; -struct rmap_private rp = { - .flags = flags, - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)flags, .done = page_mapcount_is_zero, .anon_lock = page_lock_anon_vma_read, };
@@ -1523,11 +1524,8 @@ int try_to_unmap(struct page *page, enum ttu_flags flags)else ret =rmap_walk (page, &rwc); -if (ret !=SWAP_MLOCK && !page_mapcount (page)) { +if (ret !=SWAP_MLOCK && !page_mapcount (page)) ret =SWAP_SUCCESS ; -if (rp.lazyfreed && !PageDirty (page)) - ret =SWAP_LZFREE ; - }return ret; }
@@ -1554,14 +1552,10 @@ static int page_not_mapped(struct page *page)int try_to_munlock (struct page *page) {int ret; -struct rmap_private rp = { - .flags =TTU_MUNLOCK , - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)TTU_MUNLOCK , .done = page_not_mapped, .anon_lock = page_lock_anon_vma_read,
mm/vmscan.c +22 -12
@@ -911,7 +911,8 @@ static void page_check_dirty_writeback(struct page *page,* Anonymous pages are not handled by flushers and must be written * from reclaim context. Do not stall reclaim based on them */ -if (!page_is_file_cache (page)) { +if (!page_is_file_cache (page) || + (PageAnon (page) && !PageSwapBacked (page))) { *dirty = false; *writeback = false;return ;
@@ -992,7 +993,8 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;/* Double the slab pressure for mapped and swapcache pages */ -if (page_mapped (page) ||PageSwapCache (page)) +if ((page_mapped (page) ||PageSwapCache (page)) && + !(PageAnon (page) && !PageSwapBacked (page))) sc->nr_scanned++; may_enter_fs = (sc->gfp_mask & __GFP_FS) ||
@@ -1118,8 +1120,10 @@ static unsigned long shrink_page_list(struct list_head *page_list,/* * Anonymous process memory has backing store? * Try to allocate it some swap space here. +* Lazyfree page could be freed directly */ -if (PageAnon (page) && !PageSwapCache (page)) { +if (PageAnon (page) &&PageSwapBacked (page) && + !PageSwapCache (page)) {if (!(sc->gfp_mask & __GFP_IO)) goto keep_locked;if (!add_to_swap (page, page_list))
@@ -1140,9 +1144,12 @@ static unsigned long shrink_page_list(struct list_head *page_list,* The page is mapped into the page tables of one or more * processes. Try to unmap it here. */ -if (page_mapped (page) && mapping) { +if (page_mapped (page)) {switch (ret =try_to_unmap (page, ttu_flags |TTU_BATCH_FLUSH )) { +case SWAP_DIRTY : +SetPageSwapBacked (page); +/* fall through */ case SWAP_FAIL : nr_unmap_fail++; goto activate_locked;
@@ -1150,8 +1157,6 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;case SWAP_MLOCK : goto cull_mlocked; -case SWAP_LZFREE : - goto lazyfree;case SWAP_SUCCESS : ;/* try to free the page below */ }
@@ -1263,10 +1268,18 @@ static unsigned long shrink_page_list(struct list_head *page_list, } } -lazyfree: -if (!mapping || !__remove_mapping (mapping, page, true)) - goto keep_locked; +if (PageAnon (page) && !PageSwapBacked (page)) { +/* follow __remove_mapping for reference */ +if (!page_ref_freeze (page,1 )) + goto keep_locked; +if (PageDirty (page)) { +page_ref_unfreeze (page,1 ); + goto keep_locked; + } +count_vm_event (PGLAZYFREED ); + }else if (!mapping || !__remove_mapping (mapping, page, true)) + goto keep_locked;/* * At this point, we have no other references and there is * no way to pick any more up (removed from LRU, removed
@@ -1276,9 +1289,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,*/ __ClearPageLocked (page); free_it: -if (ret ==SWAP_LZFREE ) -count_vm_event (PGLAZYFREED ); - nr_reclaimed++;/*
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
Hi Shaohua,
Quoted 34 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>--- include/linux/rmap.h | 2 +- mm/huge_memory.c | 2 ++ mm/madvise.c | 1 + mm/rmap.c | 40 +++++++++++++++++----------------------- mm/vmscan.c | 34 ++++++++++++++++++++++------------ 5 files changed, 43 insertions(+), 36 deletions(-)include/linux/rmap.h +0
-0
include/linux/rmap.h static inline int page_mkclean(struct page *page) · line 301
Quoted 5 lines
include/linux/rmap.h +1
-1@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4
I still don't convinced why we should introduce SWAP_DIRTY in try_to_unmap.
https://marc.info/?l=linux-mm&m=148797879123238&w=2
We have been SetPageMlocked in there but why cannot we SetPageSwapBacked in there? It's not a thing to change LRU type but it's just indication we found the page's status changed in late.
Quoted 226 lines
include/linux/rmap.h +0
-0#endif /* _LINUX_RMAP_H */ mm/huge_memory.c +2
-0@@ -1571,6 +1571,8 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma,set_pmd_at (mm, addr, pmd, orig_pmd);tlb_remove_pmd_tlb_entry (tlb, pmd, addr); } + +mark_page_lazyfree (page); ret = true; out:spin_unlock (ptl);mm/madvise.c +1
-0@@ -413,6 +413,7 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,set_pte_at (mm, addr, pte, ptent);tlb_remove_tlb_entry (tlb, pte, addr); } +mark_page_lazyfree (page); } out:if (nr_swap) {mm/rmap.c +17
-23@@ -1281,11 +1281,6 @@ void page_remove_rmap(struct page *page, bool compound)*/ } -struct rmap_private { -enum ttu_flags flags; -int lazyfreed; -}; -/* * @arg: enum ttu_flags will be passed to this argument */ @@ -1301,8 +1296,7 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,pte_t pteval;struct page *subpage;int ret =SWAP_AGAIN ; -struct rmap_private *rp = arg; -enum ttu_flags flags = rp->flags; +enum ttu_flags flags = (enum ttu_flags )arg;/* munlock has nothing to gain from examining un-locked vmas */ if ((flags &TTU_MUNLOCK ) && !(vma->vm_flags &VM_LOCKED ))@@ -1419,11 +1413,21 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), page); -if (!PageDirty (page)) { +/* +* swapin page could be clean, it has data stored in +* swap. We can't silently discard it without setting +* swap entry in the page table. +*/ +if (!PageDirty (page) && !PageSwapCache (page)) {/* It's a freeable page by MADV_FREE */ dec_mm_counter (mm,MM_ANONPAGES ); - rp->lazyfreed++; goto discard; + }else if (!PageSwapBacked (page)) { +/* dirty MADV_FREE page */ +set_pte_at (mm, address, pvmw.pte, pteval); + ret =SWAP_DIRTY ; +page_vma_mapped_walk_done (&pvmw); +break ; }if (swap_duplicate (entry) <0 ) {@@ -1491,18 +1495,15 @@ static int page_mapcount_is_zero(struct page *page)* SWAP_AGAIN - we missed a mapping, try again later * SWAP_FAIL - the page is unswappable * SWAP_MLOCK - page is mlocked. +* SWAP_DIRTY - page is dirty MADV_FREE page */ int try_to_unmap (struct page *page,enum ttu_flags flags) {int ret; -struct rmap_private rp = { - .flags = flags, - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)flags, .done = page_mapcount_is_zero, .anon_lock = page_lock_anon_vma_read, };@@ -1523,11 +1524,8 @@ int try_to_unmap(struct page *page, enum ttu_flags flags)else ret =rmap_walk (page, &rwc); -if (ret !=SWAP_MLOCK && !page_mapcount (page)) { +if (ret !=SWAP_MLOCK && !page_mapcount (page)) ret =SWAP_SUCCESS ; -if (rp.lazyfreed && !PageDirty (page)) - ret =SWAP_LZFREE ; - }return ret; }@@ -1554,14 +1552,10 @@ static int page_not_mapped(struct page *page)int try_to_munlock (struct page *page) {int ret; -struct rmap_private rp = { - .flags =TTU_MUNLOCK , - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)TTU_MUNLOCK , .done = page_not_mapped, .anon_lock = page_lock_anon_vma_read,mm/vmscan.c +22
-12@@ -911,7 +911,8 @@ static void page_check_dirty_writeback(struct page *page,* Anonymous pages are not handled by flushers and must be written * from reclaim context. Do not stall reclaim based on them */ -if (!page_is_file_cache (page)) { +if (!page_is_file_cache (page) || + (PageAnon (page) && !PageSwapBacked (page))) { *dirty = false; *writeback = false;return ;@@ -992,7 +993,8 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;/* Double the slab pressure for mapped and swapcache pages */ -if (page_mapped (page) ||PageSwapCache (page)) +if ((page_mapped (page) ||PageSwapCache (page)) && + !(PageAnon (page) && !PageSwapBacked (page))) sc->nr_scanned++; may_enter_fs = (sc->gfp_mask & __GFP_FS) ||@@ -1118,8 +1120,10 @@ static unsigned long shrink_page_list(struct list_head *page_list,/* * Anonymous process memory has backing store? * Try to allocate it some swap space here. +* Lazyfree page could be freed directly */ -if (PageAnon (page) && !PageSwapCache (page)) { +if (PageAnon (page) &&PageSwapBacked (page) && + !PageSwapCache (page)) {if (!(sc->gfp_mask & __GFP_IO)) goto keep_locked;if (!add_to_swap (page, page_list))@@ -1140,9 +1144,12 @@ static unsigned long shrink_page_list(struct list_head *page_list,* The page is mapped into the page tables of one or more * processes. Try to unmap it here. */ -if (page_mapped (page) && mapping) { +if (page_mapped (page)) {switch (ret =try_to_unmap (page, ttu_flags |TTU_BATCH_FLUSH )) { +case SWAP_DIRTY : +SetPageSwapBacked (page); +/* fall through */ case SWAP_FAIL : nr_unmap_fail++; goto activate_locked;@@ -1150,8 +1157,6 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;case SWAP_MLOCK : goto cull_mlocked; -case SWAP_LZFREE : - goto lazyfree;case SWAP_SUCCESS : ;/* try to free the page below */ }@@ -1263,10 +1268,18 @@ static unsigned long shrink_page_list(struct list_head *page_list, } } -lazyfree: -if (!mapping || !__remove_mapping (mapping, page, true)) - goto keep_locked; +if (PageAnon (page) && !PageSwapBacked (page)) { +/* follow __remove_mapping for reference */ +if (!page_ref_freeze (page,1 )) + goto keep_locked; +if (PageDirty (page)) { +page_ref_unfreeze (page,1 ); + goto keep_locked; + } +count_vm_event (PGLAZYFREED ); + }else if (!mapping || !__remove_mapping (mapping, page, true)) + goto keep_locked;/* * At this point, we have no other references and there is * no way to pick any more up (removed from LRU, removed @@ -1276,9 +1289,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,*/ __ClearPageLocked (page); free_it: -if (ret ==SWAP_LZFREE ) -count_vm_event (PGLAZYFREED ); - nr_reclaimed++;/* Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
Quoted 46 lines · Minchan Kim
Hi Shaohua,
Quoted 34 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>--- include/linux/rmap.h | 2 +- mm/huge_memory.c | 2 ++ mm/madvise.c | 1 + mm/rmap.c | 40 +++++++++++++++++----------------------- mm/vmscan.c | 34 ++++++++++++++++++++++------------ 5 files changed, 43 insertions(+), 36 deletions(-)include/linux/rmap.h +0
-0include/linux/rmap.h static inline int page_mkclean(struct page *page) · line 301
Quoted 5 lines
include/linux/rmap.h +1
-1@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4I still don't convinced why we should introduce
SWAP_DIRTYintry_to_unmap.
https://marc.info/?l=linux-mm&m=148797879123238&w=2
Quoted 3 lines
We have been SetPageMlocked in there but why cannot we SetPageSwapBacked in there? It's not a thing to change LRU type but it's just indication we found the page's status changed in late.
This one I don't have strong preference. Personally I agree with Johannes, handling failure in vmscan sounds better. But since the failure handling is just one statement, this probably doesn't make too much difference. If Johannes and you made an agreement, I'll follow.
Thanks,
Shaohua
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
Quoted 1 line · Shaohua Li
On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote:
[...]
Quoted 12 lines
Quoted 12 lines
include/linux/rmap.h static inline int page_mkclean(struct page *page) · line 301
Quoted 8 lines
include/linux/rmap.h +1
-1@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4I still don't convinced why we should introduce
SWAP_DIRTYintry_to_unmap.
https://marc.info/?l=linux-mm&m=148797879123238&w=2
Quoted 8 lines
Quoted 3 lines
We have been SetPageMlocked in there but why cannot we SetPageSwapBacked in there? It's not a thing to change LRU type but it's just indication we found the page's status changed in late.
This one I don't have strong preference. Personally I agree with Johannes, handling failure in vmscan sounds better. But since the failure handling is just one statement, this probably doesn't make too much difference. If Johannes and you made an agreement, I'll follow.
FWIW I like your current SWAP_DIRTY and the later handling at the vmscan level more.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Minchan Kim
Acked-byRe: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
In reply to Shaohua LiQuoted 47 lines · Shaohua Li
Quoted 46 lines · Minchan Kim
Hi Shaohua,
Quoted 34 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>--- include/linux/rmap.h | 2 +- mm/huge_memory.c | 2 ++ mm/madvise.c | 1 + mm/rmap.c | 40 +++++++++++++++++----------------------- mm/vmscan.c | 34 ++++++++++++++++++++++------------ 5 files changed, 43 insertions(+), 36 deletions(-)include/linux/rmap.h +0
-0include/linux/rmap.h static inline int page_mkclean(struct page *page) · line 301
Quoted 5 lines
include/linux/rmap.h +1
-1@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4I still don't convinced why we should introduce
SWAP_DIRTYintry_to_unmap.
https://marc.info/?l=linux-mm&m=148797879123238&w=2
Quoted 8 lines
Quoted 3 lines
We have been SetPageMlocked in there but why cannot we SetPageSwapBacked in there? It's not a thing to change LRU type but it's just indication we found the page's status changed in late.
This one I don't have strong preference. Personally I agree with Johannes, handling failure in vmscan sounds better. But since the failure handling is just one statement, this probably doesn't make too much difference. If Johannes and you made an agreement, I'll follow.
I don't want to add unnecessary new return value(i.e., SWAP_DIRTY). If VM found lazyfree page dirty in try_to_unmap_one, it means "non-swappable page" so it's natural to set SetPageSwapBacked in there and return just SWAP_FAIL to activate it in vmscan.c. SWAP_FAIL means the page is non-swappable so it should be activated. I don't see any problem in there like software engineering pov.
However, it seems everyone are happy with introdcuing SWAP_DIRTY so I don't insist on it which is not critical for this patchset.
I looked over try_to_unmap and callers. Now, I think we could remove SWAP_MLOCK and maybe SWAP_AGAIN as well as SWAP_DIRTY that is to make try_to_unmap *bool*. So, it could be done by separate patchset. I will look into that in more.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
In reply to Shaohua LiQuoted 6 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.
Quoted 6 lines
We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
OK, this looks much more cleaner and easier to follow than the original version I have seen.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 239 lines
--- include/linux/rmap.h | 2 +- mm/huge_memory.c | 2 ++ mm/madvise.c | 1 + mm/rmap.c | 40 +++++++++++++++++----------------------- mm/vmscan.c | 34 ++++++++++++++++++++++------------ 5 files changed, 43 insertions(+), 36 deletions(-)include/linux/rmap.h +1
-1@@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page)#define SWAP_AGAIN 1#define SWAP_FAIL 2#define SWAP_MLOCK 3 -#define SWAP_LZFREE 4 +#define SWAP_DIRTY 4#endif /* _LINUX_RMAP_H */ mm/huge_memory.c +2
-0@@ -1571,6 +1571,8 @@ bool madvise_free_huge_pmd(struct mmu_gather *tlb, struct vm_area_struct *vma,set_pmd_at (mm, addr, pmd, orig_pmd);tlb_remove_pmd_tlb_entry (tlb, pmd, addr); } + +mark_page_lazyfree (page); ret = true; out:spin_unlock (ptl);mm/madvise.c +1
-0@@ -413,6 +413,7 @@ static int madvise_free_pte_range(pmd_t *pmd, unsigned long addr,set_pte_at (mm, addr, pte, ptent);tlb_remove_tlb_entry (tlb, pte, addr); } +mark_page_lazyfree (page); } out:if (nr_swap) {mm/rmap.c +17
-23@@ -1281,11 +1281,6 @@ void page_remove_rmap(struct page *page, bool compound)*/ } -struct rmap_private { -enum ttu_flags flags; -int lazyfreed; -}; -/* * @arg: enum ttu_flags will be passed to this argument */ @@ -1301,8 +1296,7 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,pte_t pteval;struct page *subpage;int ret =SWAP_AGAIN ; -struct rmap_private *rp = arg; -enum ttu_flags flags = rp->flags; +enum ttu_flags flags = (enum ttu_flags )arg;/* munlock has nothing to gain from examining un-locked vmas */ if ((flags &TTU_MUNLOCK ) && !(vma->vm_flags &VM_LOCKED ))@@ -1419,11 +1413,21 @@ static int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,VM_BUG_ON_PAGE (!PageSwapCache (page) &&PageSwapBacked (page), page); -if (!PageDirty (page)) { +/* +* swapin page could be clean, it has data stored in +* swap. We can't silently discard it without setting +* swap entry in the page table. +*/ +if (!PageDirty (page) && !PageSwapCache (page)) {/* It's a freeable page by MADV_FREE */ dec_mm_counter (mm,MM_ANONPAGES ); - rp->lazyfreed++; goto discard; + }else if (!PageSwapBacked (page)) { +/* dirty MADV_FREE page */ +set_pte_at (mm, address, pvmw.pte, pteval); + ret =SWAP_DIRTY ; +page_vma_mapped_walk_done (&pvmw); +break ; }if (swap_duplicate (entry) <0 ) {@@ -1491,18 +1495,15 @@ static int page_mapcount_is_zero(struct page *page)* SWAP_AGAIN - we missed a mapping, try again later * SWAP_FAIL - the page is unswappable * SWAP_MLOCK - page is mlocked. +* SWAP_DIRTY - page is dirty MADV_FREE page */ int try_to_unmap (struct page *page,enum ttu_flags flags) {int ret; -struct rmap_private rp = { - .flags = flags, - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)flags, .done = page_mapcount_is_zero, .anon_lock = page_lock_anon_vma_read, };@@ -1523,11 +1524,8 @@ int try_to_unmap(struct page *page, enum ttu_flags flags)else ret =rmap_walk (page, &rwc); -if (ret !=SWAP_MLOCK && !page_mapcount (page)) { +if (ret !=SWAP_MLOCK && !page_mapcount (page)) ret =SWAP_SUCCESS ; -if (rp.lazyfreed && !PageDirty (page)) - ret =SWAP_LZFREE ; - }return ret; }@@ -1554,14 +1552,10 @@ static int page_not_mapped(struct page *page)int try_to_munlock (struct page *page) {int ret; -struct rmap_private rp = { - .flags =TTU_MUNLOCK , - .lazyfreed =0 , - };struct rmap_walk_control rwc = { .rmap_one = try_to_unmap_one, - .arg = &rp, + .arg = (void *)TTU_MUNLOCK , .done = page_not_mapped, .anon_lock = page_lock_anon_vma_read,mm/vmscan.c +22
-12@@ -911,7 +911,8 @@ static void page_check_dirty_writeback(struct page *page,* Anonymous pages are not handled by flushers and must be written * from reclaim context. Do not stall reclaim based on them */ -if (!page_is_file_cache (page)) { +if (!page_is_file_cache (page) || + (PageAnon (page) && !PageSwapBacked (page))) { *dirty = false; *writeback = false;return ;@@ -992,7 +993,8 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;/* Double the slab pressure for mapped and swapcache pages */ -if (page_mapped (page) ||PageSwapCache (page)) +if ((page_mapped (page) ||PageSwapCache (page)) && + !(PageAnon (page) && !PageSwapBacked (page))) sc->nr_scanned++; may_enter_fs = (sc->gfp_mask & __GFP_FS) ||@@ -1118,8 +1120,10 @@ static unsigned long shrink_page_list(struct list_head *page_list,/* * Anonymous process memory has backing store? * Try to allocate it some swap space here. +* Lazyfree page could be freed directly */ -if (PageAnon (page) && !PageSwapCache (page)) { +if (PageAnon (page) &&PageSwapBacked (page) && + !PageSwapCache (page)) {if (!(sc->gfp_mask & __GFP_IO)) goto keep_locked;if (!add_to_swap (page, page_list))@@ -1140,9 +1144,12 @@ static unsigned long shrink_page_list(struct list_head *page_list,* The page is mapped into the page tables of one or more * processes. Try to unmap it here. */ -if (page_mapped (page) && mapping) { +if (page_mapped (page)) {switch (ret =try_to_unmap (page, ttu_flags |TTU_BATCH_FLUSH )) { +case SWAP_DIRTY : +SetPageSwapBacked (page); +/* fall through */ case SWAP_FAIL : nr_unmap_fail++; goto activate_locked;@@ -1150,8 +1157,6 @@ static unsigned long shrink_page_list(struct list_head *page_list, goto keep_locked;case SWAP_MLOCK : goto cull_mlocked; -case SWAP_LZFREE : - goto lazyfree;case SWAP_SUCCESS : ;/* try to free the page below */ }@@ -1263,10 +1268,18 @@ static unsigned long shrink_page_list(struct list_head *page_list, } } -lazyfree: -if (!mapping || !__remove_mapping (mapping, page, true)) - goto keep_locked; +if (PageAnon (page) && !PageSwapBacked (page)) { +/* follow __remove_mapping for reference */ +if (!page_ref_freeze (page,1 )) + goto keep_locked; +if (PageDirty (page)) { +page_ref_unfreeze (page,1 ); + goto keep_locked; + } +count_vm_event (PGLAZYFREED ); + }else if (!mapping || !__remove_mapping (mapping, page, true)) + goto keep_locked;/* * At this point, we have no other references and there is * no way to pick any more up (removed from LRU, removed @@ -1276,9 +1289,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,*/ __ClearPageLocked (page); free_it: -if (ret ==SWAP_LZFREE ) -count_vm_event (PGLAZYFREED ); - nr_reclaimed++;/* Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
In reply to Shaohua LiQuoted 13 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>
FWIW, I agree with Minchan that this could be folded into the previous patch and would be a little neater. But I don't feel strongly in this case since I didn't have any trouble reviewing the patches like this - void mark_page_lazyfree(struct page *) is an easy API to remember.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages
In reply to Shaohua LiQuoted 22 lines · Shaohua Li
When memory pressure is high, we free
MADV_FREEpages. If the pages are not dirty in pte, the pages could be freed immediately. Otherwise we can't reclaim them. We put the pages back to anonumous LRU list (by setting SwapBacked flag) and the pages will be reclaimed in normal swapout way.We use normal page reclaim policy. Since
MADV_FREEpages are put into inactive file list, such pages and inactive file pages are reclaimed according to their age. This is expected, because we don't want to reclaim too manyMADV_FREEpages before used once pages.Based on Minchan's original patch
Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Johannes Weiner <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 1 line
---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 5/6 mm: enable MADV_FREE for swapless system
In reply to Shaohua LiNow MADV_FREE pages can be easily reclaimed even for swapless system. We can safely enable MADV_FREE for all systems.
--- mm/madvise.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)
mm/madvise.c +1 -7
@@ -612,13 +612,7 @@ madvise_vma(struct vm_area_struct *vma, struct vm_area_struct **prev,case MADV_WILLNEED :return madvise_willneed (vma, prev, start, end);case MADV_FREE : -/* -* XXX: In this implementation, MADV_FREE works like -* MADV_DONTNEED on swapless system or full swap. -*/ -if (get_nr_swap_pages () >0 ) -return madvise_free (vma, prev, start, end); -/* passthrough */ +return madvise_free (vma, prev, start, end);case MADV_DONTNEED :return madvise_dontneed (vma, prev, start, end);default :
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system
Quoted 11 lines · Shaohua Li
Now
MADV_FREEpages can be easily reclaimed even for swapless system. We can safely enableMADV_FREEfor all systems.Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 26 lines
--- mm/madvise.c | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-)mm/madvise.c +1
-7@@ -612,13 +612,7 @@ madvise_vma(struct vm_area_struct *vma, struct vm_area_struct **prev,case MADV_WILLNEED :return madvise_willneed (vma, prev, start, end);case MADV_FREE : -/* -* XXX: In this implementation, MADV_FREE works like -* MADV_DONTNEED on swapless system or full swap. -*/ -if (get_nr_swap_pages () >0 ) -return madvise_free (vma, prev, start, end); -/* passthrough */ +return madvise_free (vma, prev, start, end);case MADV_DONTNEED :return madvise_dontneed (vma, prev, start, end);default :Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system
In reply to Shaohua LiQuoted 12 lines · Shaohua Li
Now
MADV_FREEpages can be easily reclaimed even for swapless system. We can safely enableMADV_FREEfor all systems.Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 1 line
---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system
In reply to Shaohua LiQuoted 11 lines · Shaohua Li
Now
MADV_FREEpages can be easily reclaimed even for swapless system. We can safely enableMADV_FREEfor all systems.Cc Michal Hocko <[email protected]>Cc Minchan Kim <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Signed-off-by Shaohua Li <[email protected]>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
PATCH v5 6/6 proc: show MADV_FREE pages info in smaps
In reply to Shaohua Lishow MADV_FREE pages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirty MADV_FREE pages without notice from kernel, this interface is the only place we can get accurate accounting info about MADV_FREE pages.
--- Documentation/filesystems/proc.txt | 4 ++++ fs/proc/task_mmu.c | 8 +++++++- 2 files changed, 11 insertions(+), 1 deletion(-)
Documentation/filesystems/proc.txt +4 -0
@@ -412,6 +412,7 @@ Private_Clean: 0 kB Private_Dirty: 0 kB Referenced: 892 kB Anonymous: 0 kB +LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped: 0 kB Shared_Hugetlb: 0 kB
@@ -441,6 +442,9 @@ accessed. "Anonymous" shows the amount of memory that does not belong to any file. Even a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE and a page is modified, the file page is replaced by a private anonymous copy. +"LazyFree" shows the amount of memory which is marked by madvise(MADV_FREE). +The memory isn't freed immediately with madvise(). It's freed in memory +pressure if the memory is clean. "AnonHugePages" shows the ammount of memory backed by transparent hugepage. "ShmemPmdMapped" shows the ammount of shared (shmem/tmpfs) memory backed by huge pages.
fs/proc/task_mmu.c +7 -1
@@ -440,6 +440,7 @@ struct mem_size_stats {unsigned long private_dirty;unsigned long referenced;unsigned long anonymous; +unsigned long lazyfree;unsigned long anonymous_thp;unsigned long shmem_thp;unsigned long swap;
@@ -456,8 +457,11 @@ static void smaps_account(struct mem_size_stats *mss, struct page *page,int i, nr = compound ?1 <<compound_order (page) :1 ;unsigned long size = nr *PAGE_SIZE ; -if (PageAnon (page)) +if (PageAnon (page)) { mss->anonymous += size; +if (!PageSwapBacked (page) && !dirty && !PageDirty (page)) + mss->lazyfree += size; + } mss->resident += size;/* Accumulate the size in pages that have been accessed. */
@@ -770,6 +774,7 @@ static int show_smap(struct seq_file *m, void *v, int is_pid)"Private_Dirty: %8lu kB\n" "Referenced: %8lu kB\n" "Anonymous: %8lu kB\n" +"LazyFree: %8lu kB\n" "AnonHugePages: %8lu kB\n" "ShmemPmdMapped: %8lu kB\n" "Shared_Hugetlb: %8lu kB\n"
@@ -788,6 +793,7 @@ static int show_smap(struct seq_file *m, void *v, int is_pid) mss.private_dirty >>10 , mss.referenced >>10 , mss.anonymous >>10 , + mss.lazyfree >>10 , mss.anonymous_thp >>10 , mss.shmem_thp >>10 , mss.shared_hugetlb >> 10,
Signature · 7 lines
2.9.3 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 6 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.
Quoted 8 lines
Cc Michal Hocko <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Acked-by Minchan Kim <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 71 lines
--- Documentation/filesystems/proc.txt | 4 ++++ fs/proc/task_mmu.c | 8 +++++++- 2 files changed, 11 insertions(+), 1 deletion(-)Documentation/filesystems/proc.txt +4
-0@@ -412,6 +412,7 @@ Private_Clean: 0 kB Private_Dirty: 0 kB Referenced: 892 kB Anonymous: 0 kB +LazyFree: 0 kB AnonHugePages: 0 kB ShmemPmdMapped: 0 kB Shared_Hugetlb: 0 kB@@ -441,6 +442,9 @@ accessed. "Anonymous" shows the amount of memory that does not belong to any file. Even a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE and a page is modified, the file page is replaced by a private anonymous copy. +"LazyFree" shows the amount of memory which is marked by madvise(MADV_FREE). +The memory isn't freed immediately with madvise(). It's freed in memory +pressure if the memory is clean. "AnonHugePages" shows the ammount of memory backed by transparent hugepage. "ShmemPmdMapped" shows the ammount of shared (shmem/tmpfs) memory backed by huge pages.fs/proc/task_mmu.c +7
-1@@ -440,6 +440,7 @@ struct mem_size_stats {unsigned long private_dirty;unsigned long referenced;unsigned long anonymous; +unsigned long lazyfree;unsigned long anonymous_thp;unsigned long shmem_thp;unsigned long swap;@@ -456,8 +457,11 @@ static void smaps_account(struct mem_size_stats *mss, struct page *page,int i, nr = compound ?1 <<compound_order (page) :1 ;unsigned long size = nr *PAGE_SIZE ; -if (PageAnon (page)) +if (PageAnon (page)) { mss->anonymous += size; +if (!PageSwapBacked (page) && !dirty && !PageDirty (page)) + mss->lazyfree += size; + } mss->resident += size;/* Accumulate the size in pages that have been accessed. */ @@ -770,6 +774,7 @@ static int show_smap(struct seq_file *m, void *v, int is_pid)"Private_Dirty: %8lu kB\n" "Referenced: %8lu kB\n" "Anonymous: %8lu kB\n" +"LazyFree: %8lu kB\n" "AnonHugePages: %8lu kB\n" "ShmemPmdMapped: %8lu kB\n" "Shared_Hugetlb: %8lu kB\n" @@ -788,6 +793,7 @@ static int show_smap(struct seq_file *m, void *v, int is_pid) mss.private_dirty >>10 , mss.referenced >>10 , mss.anonymous >>10 , + mss.lazyfree >>10 , mss.anonymous_thp >>10 , mss.shmem_thp >>10 , mss.shared_hugetlb >> 10,Signature · 1 line
2.9.3
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
In reply to Shaohua LiQuoted 15 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.Cc Michal Hocko <[email protected]>Cc Hugh Dickins <[email protected]>Cc Rik van Riel <[email protected]>Cc Mel Gorman <[email protected]>Cc Andrew Morton <[email protected]>Acked-by Johannes Weiner <[email protected]>Acked-by Minchan Kim <[email protected]>Signed-off-by Shaohua Li <[email protected]>
Quoted 1 line
---
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
In reply to Shaohua LiQuoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.
I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)
Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kB
It took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simply lru_add_drain_all after we are done with the given range. We can also make this lru_lazyfree_pvecs specific but I am not sure this is worth the additional code.
---
mm/madvise.c +1 -1
@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();return 0 ; }
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 22 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kB
Quoted 7 lines
It took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.
Minchan's original patch includes a drain of pvec. I discard it because I think it's not worth the effort. There aren't too many memory in the per-cpu vecs. Like what you said, I doubt this is noticeable to userspace.
Thanks,
Shaohua
Quoted 17 lines
---
mm/madvise.c +1
-1@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();return 0 ; }Signature · 2 lines
Michal Hocko SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 31 lines · Shaohua Li
Quoted 22 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kBQuoted 7 lines
It took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.
Quoted 2 lines
Minchan's original patch includes a drain of pvec. I discard it because I think it's not worth the effort. There aren't too many memory in the per-cpu vecs.
but multiply that by the number of CPUs.
Quoted 1 line
Like what you said, I doubt this is noticeable to userspace.
maybe I wasn't clear enough. I've noticed and I expect others would as well. We really shouldn't leak implementation details like that. So I _believe_ this should be fixed. Draining all pagevecs is rather coarse but it is the simplest thing to do. If you do not want to fold this into the original patch I can send a standalone one. Or do you have any concerns about draining?
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 37 lines · Michal Hocko
Quoted 31 lines · Shaohua Li
Quoted 22 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kBQuoted 7 lines
It took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.Quoted 2 lines
Minchan's original patch includes a drain of pvec. I discard it because I think it's not worth the effort. There aren't too many memory in the per-cpu vecs.
but multiply that by the number of CPUs.
Quoted 8 lines
Quoted 1 line
Like what you said, I doubt this is noticeable to userspace.
maybe I wasn't clear enough. I've noticed and I expect others would as well. We really shouldn't leak implementation details like that. So I _believe_ this should be fixed. Draining all pagevecs is rather coarse but it is the simplest thing to do. If you do not want to fold this into the original patch I can send a standalone one. Or do you have any concerns about draining?
No, no objection at all. Just doubt it's worthy. Looks nobody complains similar issue, For exmaple, deactivate_file_page does the similar thing, then the smaps 'Referenced' could be inaccurate.
Thanks,
Shaohua
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Johannes Weiner
maintainerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
In reply to Michal HockoQuoted 35 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kBIt took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.
---mm/madvise.c +0
-0
mm/madvise.c static int madvise_free_single_vma(struct vm_area_struct *vma, · line 477
Quoted 5 lines
mm/madvise.c +1
-1@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();
A full drain on all CPUs is very expensive and IMO not justified for some per-cpu fuzz factor in the stats. I'd take hampering the stats over hampering the syscall any day; only a subset of MADV_FREE users will look at the stats.
And while the aggregate error can be large on machines with many CPUs (notably the machines on which you absolutely don't want to send IPIs to all cores each time a thread madvises some pages!), the pages of a single process are not likely to be spread out across more than a few CPUs. The error when reading a specific smaps should be completely ok.
In numbers: even if your process is madvising from 16 different CPUs, the error in its smaps file will peak at 896K in the worst case. That level of concurrency tends to come with much bigger memory quantities for that amount of error to matter.
IMO this is a non-issue.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 47 lines · Johannes Weiner
Quoted 35 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kBIt took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.
---mm/madvise.c +0
-0mm/madvise.c static int madvise_free_single_vma(struct vm_area_struct *vma, · line 477
Quoted 5 lines
mm/madvise.c +1
-1@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();A full drain on all CPUs is very expensive and IMO not justified for some per-cpu fuzz factor in the stats. I'd take hampering the stats over hampering the syscall any day; only a subset of
MADV_FREEusers will look at the stats.
Quoted 3 lines
And while the aggregate error can be large on machines with many CPUs (notably the machines on which you absolutely don't want to send IPIs to all cores each time a thread madvises some pages!),
I am not sure I understand. Where would we trigger IPIs? lru_add_drain_all relies on workqueus.
Quoted 3 lines
the pages of a
single process are not likely to be spread out across more than a few CPUs.
Then we can simply only flushe lru_lazyfree_pvecs which should reduce the unrelated noise from other pagevecs.
Quoted 6 lines
The error when reading a specific smaps should be completely ok.
In numbers: even if your process is madvising from 16 different CPUs, the error in its smaps file will peak at 896K in the worst case. That level of concurrency tends to come with much bigger memory quantities for that amount of error to matter.
It is still an unexpected behavior IMHO and an implementation detail which leaks to the userspace.
Quoted 1 line
IMO this is a non-issue.
I will not insist if there is a general consensus on this and it is a documented behavior, though.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 69 lines · Michal Hocko
Quoted 47 lines · Johannes Weiner
Quoted 35 lines · Michal Hocko
Quoted 5 lines · Shaohua Li
show
MADV_FREEpages info of each vma in smaps. The interface is for diganose or monitoring purpose, userspace could use it to understand what happens in the application. Since userspace could dirtyMADV_FREEpages without notice from kernel, this interface is the only place we can get accurate accounting info aboutMADV_FREEpages.I have just got to test this patchset and noticed something that was a bit surprising
madvise(mmap(len), len, MADV_FREE)Size: 102400 kB Rss: 102400 kB Pss: 102400 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 102400 kB Private_Dirty: 0 kB Referenced: 0 kB Anonymous: 102400 kB LazyFree: 102368 kBIt took me a some time to realize that LazyFree is not accurate because there are still pages on the per-cpu
lru_lazyfree_pvecs. I believe this is an implementation detail which shouldn't be visible to the userspace. Should we simply drain the pagevec? A crude way would be to simplylru_add_drain_allafter we are done with the given range. We can also make thislru_lazyfree_pvecsspecific but I am not sure this is worth the additional code.
---mm/madvise.c +0
-0mm/madvise.c static int madvise_free_single_vma(struct vm_area_struct *vma, · line 477
Quoted 5 lines
mm/madvise.c +1
-1@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();A full drain on all CPUs is very expensive and IMO not justified for some per-cpu fuzz factor in the stats. I'd take hampering the stats over hampering the syscall any day; only a subset of
MADV_FREEusers will look at the stats.Quoted 3 lines
And while the aggregate error can be large on machines with many CPUs (notably the machines on which you absolutely don't want to send IPIs to all cores each time a thread madvises some pages!),
I am not sure I understand. Where would we trigger IPIs?
lru_add_drain_allrelies on workqueus.Quoted 3 lines
the pages of a
single process are not likely to be spread out across more than a few CPUs.Then we can simply only flushe
lru_lazyfree_pvecswhich should reduce the unrelated noise from other pagevecs.Quoted 6 lines
The error when reading a specific smaps should be completely ok.
In numbers: even if your process is madvising from 16 different CPUs, the error in its smaps file will peak at 896K in the worst case. That level of concurrency tends to come with much bigger memory quantities for that amount of error to matter.
Quoted 7 lines
It is still an unexpected behavior IMHO and an implementation detail which leaks to the userspace.
Quoted 1 line
IMO this is a non-issue.
I will not insist if there is a general consensus on this and it is a documented behavior, though.
We cannot gurantee with that even draining because madvise_free can miss some of pages easily with several conditions.
First of all, userspace can never know how many of pages are mapped in there at the moment. As well, one of page in the range can be swapped out or is going migrating, fail to try_lockpage and so on.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Johannes Weiner
maintainerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
In reply to Michal HockoQuoted 14 lines · Michal Hocko
Quoted 13 lines · Johannes Weiner
mm/madvise.c static int madvise_free_single_vma(struct vm_area_struct *vma, · line 477
Quoted 6 lines · Michal Hocko
mm/madvise.c +1
-1@@ -474,7 +474,7 @@ static int madvise_free_single_vma(struct vm_area_struct *vma,madvise_free_page_range (&tlb, vma, start, end);mmu_notifier_invalidate_range_end (mm, start, end);tlb_finish_mmu (&tlb, start, end); - +lru_add_drain_all ();A full drain on all CPUs is very expensive and IMO not justified for some per-cpu fuzz factor in the stats. I'd take hampering the stats over hampering the syscall any day; only a subset of
MADV_FREEusers will look at the stats.
Quoted 6 lines
Quoted 3 lines
And while the aggregate error can be large on machines with many CPUs (notably the machines on which you absolutely don't want to send IPIs to all cores each time a thread madvises some pages!),
I am not sure I understand. Where would we trigger IPIs?
lru_add_drain_allrelies on workqueus.
Brainfart on my end, s,IPIs,sync work items,.
That doesn't change my point, though. These things are expensive, and we had scalability issues with them in the past. See for example 4dd72b4a47a5 ("mm: fadvise: avoid expensive remote LRU cache draining after FADV_DONTNEED").
Quoted 6 lines
Quoted 3 lines
the pages of a
single process are not likely to be spread out across more than a few CPUs.Then we can simply only flushe
lru_lazyfree_pvecswhich should reduce the unrelated noise from other pagevecs.
The problem isn't flushing other pagevecs once we're already scheduled on a CPU, the problem is scheduling work on all cpus and then waiting for completion.
Quoted 9 lines
Quoted 6 lines
The error when reading a specific smaps should be completely ok.
In numbers: even if your process is madvising from 16 different CPUs, the error in its smaps file will peak at 896K in the worst case. That level of concurrency tends to come with much bigger memory quantities for that amount of error to matter.
It is still an unexpected behavior IMHO and an implementation detail which leaks to the userspace.
We have per-cpu fuzz in every single vmstat counter. Look at calculate_normal_threshold() in vmstat.c and the sample thresholds for when per-cpu deltas are flushed. In the vast majority of machines, the per-cpu error in these counters is much higher than what we get with pagevecs holding back a few pages.
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 2 lines · Johannes Weiner
Quoted 1 line · Michal Hocko
On Wed 01-03-17 13:31:49, Johannes Weiner wrote:
[...]
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
The error when reading a specific smaps should be completely ok.
In numbers: even if your process is madvising from 16 different CPUs, the error in its smaps file will peak at 896K in the worst case. That level of concurrency tends to come with much bigger memory quantities for that amount of error to matter.
Quoted 8 lines
Quoted 2 lines
It is still an unexpected behavior IMHO and an implementation detail which leaks to the userspace.
We have per-cpu fuzz in every single vmstat counter. Look at
calculate_normal_threshold()invmstat.cand the sample thresholds for when per-cpu deltas are flushed. In the vast majority of machines, the per-cpu error in these counters is much higher than what we get with pagevecs holding back a few pages.
Yes but vmstat counters have a different usecase AFAIK. You mostly look at those when debugging or watching the system. /proc/<pid>/smaps is quite often used to do per task metrics which are then used for some decision making so it should be less fuzzy if that is possible.
Quoted 5 lines
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.
I am not aware of other counter printed in smaps that would suffer from the same problem, but I haven't checked too deeply so I might be wrong.
Anyway it seems that I am alone in my position so I will not insist. If we have any bug report then we can still fix it.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Andrew Morton
maintainerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 11 lines · On Thu, 2 Mar 2017 17:30:54 +0100 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.I am not aware of other counter printed in smaps that would suffer from the same problem, but I haven't checked too deeply so I might be wrong.
Anyway it seems that I am alone in my position so I will not insist. If we have any bug report then we can still fix it.
A single lru_add_drain_all() right at the top level (in smaps_show()?) won't kill us and should significantly improve this issue. And it might accidentally make some of the other smaps statistics more accurate as well.
If not, can we please have a nice comment somewhere appropriate which explains why LazyFree is inaccurate and why we chose to leave it that way?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Michal Hocko
reviewerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 8 lines · Andrew Morton
Quoted 6 lines · On Thu, 2 Mar 2017 17:30:54 +0100 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.
Quoted 8 lines
Quoted 5 lines
I am not aware of other counter printed in smaps that would suffer from the same problem, but I haven't checked too deeply so I might be wrong.
Anyway it seems that I am alone in my position so I will not insist. If we have any bug report then we can still fix it.
A single
lru_add_drain_all()right at the top level (insmaps_show()?) won't kill us
I do not think we want to put lru_add_drain_all cost to a random process reading /proc/<pid>/smaps. If anything the one which does the madvise should be doing this.
Quoted 7 lines
and should significantly improve this issue. And it might accidentally make some of the other smaps statistics more accurate as well.
If not, can we please have a nice comment somewhere appropriate which explains why LazyFree is inaccurate and why we chose to leave it that way?
Yeah, I would appreciate the comment more. What about the following
---
Documentation/filesystems/proc.txt +3 -1
@@ -444,7 +444,9 @@ a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE and a page is modified, the file page is replaced by a private anonymous copy. "LazyFree" shows the amount of memory which is marked by madvise(MADV_FREE). The memory isn't freed immediately with madvise(). It's freed in memory -pressure if the memory is clean. +pressure if the memory is clean. Please note that the printed value might +be lower than the real value due to optimizations used in the current +implementation. If this is not desirable please file a bug report. "AnonHugePages" shows the ammount of memory backed by transparent hugepage. "ShmemPmdMapped" shows the ammount of shared (shmem/tmpfs) memory backed by huge pages.
Signature · 8 lines
Michal Hocko SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Andrew Morton
maintainerRe: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Quoted 12 lines · On Tue, 7 Mar 2017 11:05:45 +0100 Michal Hocko <[email protected]> wrote:
Quoted 11 lines · Andrew Morton
Quoted 9 lines · On Thu, 2 Mar 2017 17:30:54 +0100 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.I am not aware of other counter printed in smaps that would suffer from the same problem, but I haven't checked too deeply so I might be wrong.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Anyway it seems that I am alone in my position so I will not insist. If we have any bug report then we can still fix it.
A single
lru_add_drain_all()right at the top level (insmaps_show()?) won't kill usI do not think we want to put
lru_add_drain_allcost to a random process reading /proc/<pid>/smaps.
Why not? It's that process which is calling for the work to be done.
Quoted 2 lines
If anything the one which does the
madvise should be doing this.
But it would be silly to do extra work in madvise() if nobody will be reading smaps for the next two months.
How much work is it anyway? What would be the relative impact upon a smaps read?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Re: [PATCH V5 6/6] proc: show MADV_FREE pages info in smaps
Hi Andrew,
Quoted 25 lines · Andrew Morton
Quoted 12 lines · On Tue, 7 Mar 2017 11:05:45 +0100 Michal Hocko <[email protected]> wrote:
Quoted 11 lines · Andrew Morton
Quoted 9 lines · On Thu, 2 Mar 2017 17:30:54 +0100 Michal Hocko <[email protected]> wrote:
Quoted 5 lines
It's not that I think you're wrong: it *is* an implementation detail. But we take a bit of incoherency from batching all over the place, so it's a little odd to take a stand over this particular instance of it
- whether demanding that it'd be fixed, or be documented, which would only suggest to users that this is special when it really isn't etc.I am not aware of other counter printed in smaps that would suffer from the same problem, but I haven't checked too deeply so I might be wrong.
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Anyway it seems that I am alone in my position so I will not insist. If we have any bug report then we can still fix it.
A single
lru_add_drain_all()right at the top level (insmaps_show()?) won't kill usI do not think we want to put
lru_add_drain_allcost to a random process reading /proc/<pid>/smaps.Why not? It's that process which is calling for the work to be done.
Quoted 8 lines
Quoted 2 lines
If anything the one which does the
madvise should be doing this.But it would be silly to do extra work in
madvise()if nobody will be reading smaps for the next two months.How much work is it anyway? What would be the relative impact upon a smaps read?
I agree only if the draining guarantees all of mapped pages in the range could be marked to lazyfree. However, it's not true because there are a few of logics to skip the page marking in madvise_free_pte_range.
So, my conclusion is drainning helps a bit but not gaurantees. In such case, IMHO, let's not do the effort to make better.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>