mm,huge,rmap: unify and speed up compound mapcounts
Subsystems (9)
cover mm,huge,rmap: unify and speed up compound mapcounts
I had intended to send just a self-explanatory 1/2 and 2/2 against 6.1-rc3 on Monday; but checked for clashes with linux-next (mainly mm-unstable) just before sending, and fuzz in mm_types.h revealed not just a clash with Sidhartha's series, but also that I had missed the hugetlb usage of tail page->private, problematic for me on 32-bit.
So that series was slightly broken; and although it would probably have been easy to fix with a "SUBPAGE_INDEX_SUBPOOL = 2" patch, that would not have moved us forward very well. So this series is against next-20221102 (and hopefully later nexts), with a preparatory 1/3 to rejig the hugetlb tail private usage, on top of Sidhartha's.
1/3 mm,hugetlb: use folio fields in second tail page 2/3 mm,thp,rmap: simplify compound page mapcount handling 3/3 mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
2/3 and 3/3 can almost be applied cleanly to 6.1-rc3 (okay when you are on 64-bit): just a couple of easily resolved rejects.
Documentation/mm/transhuge.rst | 34 +--- include/linux/hugetlb.h | 23 +-- include/linux/hugetlb_cgroup.h | 31 +-- include/linux/mm.h | 85 ++++++--- include/linux/mm_types.h | 91 ++++++--- include/linux/page-flags.h | 21 -- include/linux/rmap.h | 12 +- mm/Kconfig | 2 +- mm/debug.c | 5 +- mm/folio-compat.c | 6 - mm/huge_memory.c | 37 +--- mm/hugetlb.c | 2 + mm/khugepaged.c | 11 +- mm/memory-failure.c | 5 +- mm/page_alloc.c | 27 +-- mm/rmap.c | 359 ++++++++++++++++++++--------------- mm/util.c | 79 -------- 17 files changed, 401 insertions(+), 429 deletions(-)
Hugh
PATCH 1/3 mm,hugetlb: use folio fields in second tail page
We want to declare one more int in the first tail of a compound page:
that first tail page being valuable property, since every compound page has a first tail, but perhaps no more than that.
No problem on 64-bit: there is already space for it. No problem with 32-bit THPs: 5.18 commit 5232c63f46fd ("mm: Make compound_pincount always available") kindly cleared the space for it, apparently not realizing that only 64-bit architectures enable CONFIG_THP_SWAP (whose use of tail page->private might conflict) - but make sure of that in its Kconfig.
But hugetlb pages use tail page->private of the first tail page for a subpool pointer, which will conflict; and they also use page->private of the 2nd, 3rd and 4th tails.
Undo "mm: add private field of first tail to struct page and struct folio"'s recent addition of private_1 to the folio tail: instead add hugetlb_subpool, hugetlb_cgroup, hugetlb_cgroup_rsvd, hugetlb_hwpoison to a second tail page of the folio: THP has long been using several fields of that tail, so make better use of it for hugetlb too. This is not how a generic folio should be declared in future, but it is an effective transitional way to make use of it.
Delete the SUBPAGE_INDEX stuff, but keep __NR_USED_SUBPAGE: now 3.
--- include/linux/hugetlb.h | 23 +++-------- include/linux/hugetlb_cgroup.h | 31 +++++---------- include/linux/mm_types.h | 72 ++++++++++++++++++++++------------ mm/Kconfig | 2 +- mm/memory-failure.c | 5 +-- 5 files changed, 65 insertions(+), 68 deletions(-)
include/linux/hugetlb.h +5 -18
@@ -33,22 +33,9 @@ typedef struct { unsigned long pd; } hugepd_t;/* * For HugeTLB page, there are more metadata to save in the struct page. But * the head struct page cannot meet our needs, so we have to abuse other tail -* struct page to store the metadata. In order to avoid conflicts caused by -* subsequent use of more tail struct pages, we gather these discrete indexes -* of tail struct page here. +* struct page to store the metadata. */ -enum { -SUBPAGE_INDEX_SUBPOOL =1 ,/* reuse page->private */ -#ifdef CONFIG_CGROUP_HUGETLB -SUBPAGE_INDEX_CGROUP ,/* reuse page->private */ -SUBPAGE_INDEX_CGROUP_RSVD ,/* reuse page->private */ - __MAX_CGROUP_SUBPAGE_INDEX =SUBPAGE_INDEX_CGROUP_RSVD , -#endif -#ifdef CONFIG_MEMORY_FAILURE -SUBPAGE_INDEX_HWPOISON , -#endif - __NR_USED_SUBPAGE, -}; +#define __NR_USED_SUBPAGE 3struct hugepage_subpool {spinlock_t lock;
@@ -722,11 +709,11 @@ extern unsigned int default_hstate_idx;static inline struct hugepage_subpool *hugetlb_folio_subpool (struct folio *folio) { -return (void *)folio_get_private_1 (folio); +return folio->_hugetlb_subpool; }/* -* hugetlb page subpool pointer located in hpage[1].private +* hugetlb page subpool pointer located in hpage[2].hugetlb_subpool */ static inline struct hugepage_subpool *hugetlb_page_subpool (struct page *hpage) {
@@ -736,7 +723,7 @@ static inline struct hugepage_subpool *hugetlb_page_subpool(struct page *hpage)static inline void hugetlb_set_folio_subpool (struct folio *folio,struct hugepage_subpool *subpool) { -folio_set_private_1 (folio, (unsigned long )subpool); + folio->_hugetlb_subpool = subpool; } static inline void hugetlb_set_page_subpool(struct page *hpage,
include/linux/hugetlb_cgroup.h +9 -22
@@ -24,12 +24,10 @@ struct file_region;#ifdef CONFIG_CGROUP_HUGETLB /* * Minimum page order trackable by hugetlb cgroup. -* At least 4 pages are necessary for all the tracking information. -* The second tail page (hpage[SUBPAGE_INDEX_CGROUP]) is the fault -* usage cgroup. The third tail page (hpage[SUBPAGE_INDEX_CGROUP_RSVD]) -* is the reservation usage cgroup. +* At least 3 pages are necessary for all the tracking information. +* The second tail page contains all of the hugetlb-specific fields. */ -#define HUGETLB_CGROUP_MIN_ORDER order_base_2(__MAX_CGROUP_SUBPAGE_INDEX + 1) +#define HUGETLB_CGROUP_MIN_ORDER order_base_2(__NR_USED_SUBPAGE)enum hugetlb_memory_event { HUGETLB_MAX,
@@ -69,21 +67,13 @@ struct hugetlb_cgroup {static inline struct hugetlb_cgroup *__hugetlb_cgroup_from_folio (struct folio *folio,bool rsvd) { -struct page *tail; -VM_BUG_ON_FOLIO (!folio_test_hugetlb (folio), folio);if (folio_order (folio) <HUGETLB_CGROUP_MIN_ORDER )return NULL ; - -if (rsvd) { - tail =folio_page (folio,SUBPAGE_INDEX_CGROUP_RSVD ); -return (void *)page_private (tail); - } - -else { - tail =folio_page (folio,SUBPAGE_INDEX_CGROUP ); -return (void *)page_private (tail); - } +if (rsvd) +return folio->_hugetlb_cgroup_rsvd; +else +return folio->_hugetlb_cgroup; }static inline struct hugetlb_cgroup *hugetlb_cgroup_from_folio (struct folio *folio)
@@ -101,15 +91,12 @@ static inline void __set_hugetlb_cgroup(struct folio *folio, struct hugetlb_cgroup *h_cg, bool rsvd) {VM_BUG_ON_FOLIO (!folio_test_hugetlb (folio), folio); -if (folio_order (folio) <HUGETLB_CGROUP_MIN_ORDER )return ;if (rsvd) -set_page_private (folio_page (folio,SUBPAGE_INDEX_CGROUP_RSVD ), - (unsigned long )h_cg); + folio->_hugetlb_cgroup_rsvd = h_cg;else -set_page_private (folio_page (folio,SUBPAGE_INDEX_CGROUP ), - (unsigned long )h_cg); + folio->_hugetlb_cgroup = h_cg; } static inline void set_hugetlb_cgroup(struct folio *folio,
include/linux/mm_types.h +48 -24
124 lines not on this page · raw message
mm/Kconfig +1 -1
@@ -775,7 +775,7 @@ endchoice config THP_SWAP def_bool y - depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP + depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP && 64BIT help Swap transparent huge pages in one piece, without splitting. XXX: For now, swap cluster backing transparent huge page
mm/memory-failure.c +2 -3
@@ -1687,8 +1687,7 @@ EXPORT_SYMBOL_GPL(mf_dax_kill_procs); #ifdef CONFIG_HUGETLB_PAGE /* * Struct raw_hwp_page represents information about "raw error page", - * constructing singly linked list originated from ->private field of - * SUBPAGE_INDEX_HWPOISON-th tail page. + * constructing singly linked list from ->_hugetlb_hwpoison field of folio. */ struct raw_hwp_page { struct llist_node node;
@@ -1697,7 +1696,7 @@ struct raw_hwp_page {static inline struct llist_head *raw_hwp_list_head (struct page *hpage) { -return (struct llist_head *)&page_private (hpage +SUBPAGE_INDEX_HWPOISON ); +return (struct llist_head *)&page_folio (hpage)->_hugetlb_hwpoison; }static unsigned long __free_raw_hwp_pages (struct page *hpage,bool move_flag)
Signature · 1 line
2.35.3
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
Quoted 179 lines · Hugh Dickins
We want to declare one more int in the first tail of a compound page:
that first tail page being valuable property, since every compound page has a first tail, but perhaps no more than that.No problem on 64-bit: there is already space for it. No problem with 32-bit THPs: 5.18 commit
5232c63f46fd("mm: Makecompound_pincountalways available") kindly cleared the space for it, apparently not realizing that only 64-bit architectures enableCONFIG_THP_SWAP(whose use of tailpage->privatemight conflict) - but make sure of that in itsKconfig.But hugetlb pages use tail
page->privateof the first tail page for a subpool pointer, which will conflict; and they also usepage->privateof the 2nd, 3rd and 4th tails.Undo "mm: add private field of first tail to struct page and struct folio"'s recent addition of
private_1to the folio tail: instead addhugetlb_subpool,hugetlb_cgroup,hugetlb_cgroup_rsvd,hugetlb_hwpoisonto a second tail page of the folio: THP has long been using several fields of that tail, so make better use of it for hugetlb too. This is not how a generic folio should be declared in future, but it is an effective transitional way to make use of it.Delete the
SUBPAGE_INDEXstuff, but keep__NR_USED_SUBPAGE: now 3.Signed-off-by Hugh Dickins <[email protected]>--- include/linux/hugetlb.h | 23 +++-------- include/linux/hugetlb_cgroup.h | 31 +++++---------- include/linux/mm_types.h | 72 ++++++++++++++++++++++------------ mm/Kconfig | 2 +- mm/memory-failure.c | 5 +-- 5 files changed, 65 insertions(+), 68 deletions(-)include/linux/hugetlb.h +5
-18@@ -33,22 +33,9 @@ typedef struct { unsigned long pd; } hugepd_t;/* * For HugeTLB page, there are more metadata to save in the struct page. But * the head struct page cannot meet our needs, so we have to abuse other tail -* struct page to store the metadata. In order to avoid conflicts caused by -* subsequent use of more tail struct pages, we gather these discrete indexes -* of tail struct page here. +* struct page to store the metadata. */ -enum { -SUBPAGE_INDEX_SUBPOOL =1 ,/* reuse page->private */ -#ifdef CONFIG_CGROUP_HUGETLB -SUBPAGE_INDEX_CGROUP ,/* reuse page->private */ -SUBPAGE_INDEX_CGROUP_RSVD ,/* reuse page->private */ - __MAX_CGROUP_SUBPAGE_INDEX =SUBPAGE_INDEX_CGROUP_RSVD , -#endif -#ifdef CONFIG_MEMORY_FAILURE -SUBPAGE_INDEX_HWPOISON , -#endif - __NR_USED_SUBPAGE, -}; +#define __NR_USED_SUBPAGE 3struct hugepage_subpool {spinlock_t lock;@@ -722,11 +709,11 @@ extern unsigned int default_hstate_idx;static inline struct hugepage_subpool *hugetlb_folio_subpool (struct folio *folio) { -return (void *)folio_get_private_1 (folio); +return folio->_hugetlb_subpool; }/* -* hugetlb page subpool pointer located in hpage[1].private +* hugetlb page subpool pointer located in hpage[2].hugetlb_subpool */ static inline struct hugepage_subpool *hugetlb_page_subpool (struct page *hpage) {@@ -736,7 +723,7 @@ static inline struct hugepage_subpool *hugetlb_page_subpool(struct page *hpage)static inline void hugetlb_set_folio_subpool (struct folio *folio,struct hugepage_subpool *subpool) { -folio_set_private_1 (folio, (unsigned long )subpool); + folio->_hugetlb_subpool = subpool; } static inline void hugetlb_set_page_subpool(struct page *hpage,include/linux/hugetlb_cgroup.h +9
-22@@ -24,12 +24,10 @@ struct file_region;#ifdef CONFIG_CGROUP_HUGETLB /* * Minimum page order trackable by hugetlb cgroup. -* At least 4 pages are necessary for all the tracking information. -* The second tail page (hpage[SUBPAGE_INDEX_CGROUP]) is the fault -* usage cgroup. The third tail page (hpage[SUBPAGE_INDEX_CGROUP_RSVD]) -* is the reservation usage cgroup. +* At least 3 pages are necessary for all the tracking information. +* The second tail page contains all of the hugetlb-specific fields. */ -#define HUGETLB_CGROUP_MIN_ORDER order_base_2(__MAX_CGROUP_SUBPAGE_INDEX + 1) +#define HUGETLB_CGROUP_MIN_ORDER order_base_2(__NR_USED_SUBPAGE)enum hugetlb_memory_event { HUGETLB_MAX,@@ -69,21 +67,13 @@ struct hugetlb_cgroup {static inline struct hugetlb_cgroup *__hugetlb_cgroup_from_folio (struct folio *folio,bool rsvd) { -struct page *tail; -VM_BUG_ON_FOLIO (!folio_test_hugetlb (folio), folio);if (folio_order (folio) <HUGETLB_CGROUP_MIN_ORDER )return NULL ; - -if (rsvd) { - tail =folio_page (folio,SUBPAGE_INDEX_CGROUP_RSVD ); -return (void *)page_private (tail); - } - -else { - tail =folio_page (folio,SUBPAGE_INDEX_CGROUP ); -return (void *)page_private (tail); - } +if (rsvd) +return folio->_hugetlb_cgroup_rsvd; +else +return folio->_hugetlb_cgroup; }static inline struct hugetlb_cgroup *hugetlb_cgroup_from_folio (struct folio *folio)@@ -101,15 +91,12 @@ static inline void __set_hugetlb_cgroup(struct folio *folio, struct hugetlb_cgroup *h_cg, bool rsvd) {VM_BUG_ON_FOLIO (!folio_test_hugetlb (folio), folio); -if (folio_order (folio) <HUGETLB_CGROUP_MIN_ORDER )return ;if (rsvd) -set_page_private (folio_page (folio,SUBPAGE_INDEX_CGROUP_RSVD ), - (unsigned long )h_cg); + folio->_hugetlb_cgroup_rsvd = h_cg;else -set_page_private (folio_page (folio,SUBPAGE_INDEX_CGROUP ), - (unsigned long )h_cg); + folio->_hugetlb_cgroup = h_cg; } static inline void set_hugetlb_cgroup(struct folio *folio,include/linux/mm_types.h +9
-2@@ -145,15 +145,22 @@ struct page {atomic_t compound_pincount;#ifdef CONFIG_64BIT unsigned int compound_nr;/* 1 << compound_order */ -unsigned long _private_1;#endif }; -struct {/* Second tail page of compound page */ +struct {/* Second tail page of transparent huge page */ unsigned long _compound_pad_1;/* compound_head */ unsigned long _compound_pad_2;/* For both global and memcg */ struct list_head deferred_list; }; +struct {/* Second tail page of hugetlb page */ +unsigned long _hugetlb_pad_1;/* compound_head */ +void *hugetlb_subpool; +void *hugetlb_cgroup; +void *hugetlb_cgroup_rsvd; +void *hugetlb_hwpoison; +/* No more space on 32-bit: use third tail if more */ + };struct {/* Page table pages */ unsigned long _pt_pad_1;/* compound_head */ pgtable_t pmd_huge_pte;/* protected by page->ptl */
include/linux/mm_types.h struct page { · line 270
Quoted 5 lines
include/linux/mm_types.h +1
-1@@ -260,13 +267,16 @@ struct page {* to find how many references there are to this folio. * @memcg_data: Memory Control Group data. * @_flags_1: For large folios, additional page flags. -* @__head: Points to the folio. Do not use. +* @_head_1: Points to the folio. Do not use.
Changes to my original patch set look good, this seems to be a cleaner implementation.
Should the usage of page_1 and page_2 also be documented here?
Thanks,
Sidhartha Kumar
Quoted 134 lines
include/linux/mm_types.h +38
-21* @_folio_dtor: Which destructor to use for this folio. * @_folio_order: Do not use directly, call folio_order(). * @_total_mapcount: Do not use directly, call folio_entire_mapcount(). * @_pincount: Do not use directly, call folio_maybe_dma_pinned(). * @_folio_nr_pages: Do not use directly, call folio_nr_pages(). -* @_private_1: Do not use directly, call folio_get_private_1(). +* @_hugetlb_subpool: Do not use directly, use accessor in hugetlb.h. +* @_hugetlb_cgroup: Do not use directly, use accessor in hugetlb_cgroup.h. +* @_hugetlb_cgroup_rsvd: Do not use directly, use accessor in hugetlb_cgroup.h. +* @_hugetlb_hwpoison: Do not use directly, call raw_hwp_list_head(). * * A folio is a physically, virtually and logically contiguous set * of bytes. It is a power-of-two in size, and it is aligned to that @@ -305,16 +315,31 @@ struct folio { };struct page page; }; -unsigned long _flags_1; -unsigned long __head; -unsigned char _folio_dtor; -unsigned char _folio_order; -atomic_t _total_mapcount; -atomic_t _pincount; +union { +struct { +unsigned long _flags_1; +unsigned long _head_1; +unsigned char _folio_dtor; +unsigned char _folio_order; +atomic_t _total_mapcount; +atomic_t _pincount;#ifdef CONFIG_64BIT -unsigned int _folio_nr_pages; +unsigned int _folio_nr_pages;#endif -unsigned long _private_1; + }; +struct page page_1; + }; +union { +struct { +unsigned long _flags_2; +unsigned long _head_2; +void *_hugetlb_subpool; +void *_hugetlb_cgroup; +void *_hugetlb_cgroup_rsvd; +void *_hugetlb_hwpoison; + }; +struct page page_2; + }; };#define FOLIO_MATCH (pg, fl) \@@ -335,16 +360,25 @@ FOLIO_MATCH(memcg_data, memcg_data);static_assert (offsetof(struct folio , fl) == \ offsetof(struct page, pg) + sizeof(struct page))FOLIO_MATCH (flags, _flags_1); -FOLIO_MATCH (compound_head, __head); +FOLIO_MATCH (compound_head, _head_1);FOLIO_MATCH (compound_dtor, _folio_dtor);FOLIO_MATCH (compound_order, _folio_order);FOLIO_MATCH (compound_mapcount, _total_mapcount);FOLIO_MATCH (compound_pincount, _pincount);#ifdef CONFIG_64BIT FOLIO_MATCH (compound_nr, _folio_nr_pages); -FOLIO_MATCH (_private_1, _private_1);#endif #undef FOLIO_MATCH +#define FOLIO_MATCH (pg, fl) \ + static_assert(offsetof(struct folio, fl) == \ + offsetof(struct page, pg) + 2 * sizeof(struct page)) +FOLIO_MATCH (flags, _flags_2); +FOLIO_MATCH (compound_head, _head_2); +FOLIO_MATCH (hugetlb_subpool, _hugetlb_subpool); +FOLIO_MATCH (hugetlb_cgroup, _hugetlb_cgroup); +FOLIO_MATCH (hugetlb_cgroup_rsvd, _hugetlb_cgroup_rsvd); +FOLIO_MATCH (hugetlb_hwpoison, _hugetlb_hwpoison); +#undef FOLIO_MATCHstatic inline atomic_t *folio_mapcount_ptr (struct folio *folio) {@@ -388,16 +422,6 @@ static inline void *folio_get_private(struct folio *folio)return folio->private; } -static inline void folio_set_private_1 (struct folio *folio,unsigned long private) -{ - folio->_private_1 = private; -} - -static inline unsigned long folio_get_private_1 (struct folio *folio) -{ -return folio->_private_1; -} -struct page_frag_cache {void * va;#if (PAGE_SIZE <PAGE_FRAG_CACHE_MAX_SIZE )mm/Kconfig +1
-1@@ -775,7 +775,7 @@ endchoice config THP_SWAP def_bool y - depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP + depends on TRANSPARENT_HUGEPAGE && ARCH_WANTS_THP_SWAP && SWAP && 64BIT help Swap transparent huge pages in one piece, without splitting. XXX: For now, swap cluster backing transparent huge pagemm/memory-failure.c +2
-3@@ -1687,8 +1687,7 @@ EXPORT_SYMBOL_GPL(mf_dax_kill_procs); #ifdef CONFIG_HUGETLB_PAGE /* * Struct raw_hwp_page represents information about "raw error page", - * constructing singly linked list originated from ->private field of - * SUBPAGE_INDEX_HWPOISON-th tail page. + * constructing singly linked list from ->_hugetlb_hwpoison field of folio. */ struct raw_hwp_page { struct llist_node node;@@ -1697,7 +1696,7 @@ struct raw_hwp_page {static inline struct llist_head *raw_hwp_list_head (struct page *hpage) { -return (struct llist_head *)&page_private (hpage +SUBPAGE_INDEX_HWPOISON ); +return (struct llist_head *)&page_folio (hpage)->_hugetlb_hwpoison; }static unsigned long __free_raw_hwp_pages (struct page *hpage,bool move_flag)
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
Quoted 1 line · Sidhartha Kumar
On 11/2/22 6:48 PM, Hugh Dickins wrote:
...
Quoted 7 lines
Quoted 7 lines
Undo "mm: add private field of first tail to struct page and struct folio"'s recent addition of
private_1to the folio tail: instead addhugetlb_subpool,hugetlb_cgroup,hugetlb_cgroup_rsvd,hugetlb_hwpoisonto a second tail page of the folio: THP has long been using several fields of that tail, so make better use of it for hugetlb too. This is not how a generic folio should be declared in future, but it is an effective transitional way to make use of it.
...
Quoted 9 lines
include/linux/mm_types.h struct page { · line 270
Quoted 6 lines
include/linux/mm_types.h +1
-1@@ -260,13 +267,16 @@ struct page {* to find how many references there are to this folio. * @memcg_data: Memory Control Group data. * @_flags_1: For large folios, additional page flags. -* @__head: Points to the folio. Do not use. +* @_head_1: Points to the folio. Do not use. Changes to my original patch set look good, this seems to be a cleaner implementation.
Thanks a lot, Sidhartha, I'm glad to hear that it works for you too.
I expect that it will be done differently in the future: maybe generalizing the additional fields to further "private"s as you did, letting different subsystems accessorize them differently; or removing them completely from struct folio, letting subsystems declare their own struct folio containers. I don't know how that will end up, but this for now seems good and clear.
Quoted 2 lines
Should the usage of
page_1andpage_2also be documented here?
You must have something interesting in mind to document about them, but I cannot guess what! They are for field alignment, not for use. (page_2 to help when/if someone needs to add another pageful.)
Do you mean that I should copy the
/* private: the union with struct page is transitional */
comment from above the original "struct page page;" line I copied? Or give all three of them a few underscores to imply not for use?
Thanks,
Hugh
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
Quoted 28 lines · Hugh Dickins
Quoted 1 line · Sidhartha Kumar
On 11/2/22 6:48 PM, Hugh Dickins wrote:
...
Quoted 7 lines
Quoted 7 lines
Undo "mm: add private field of first tail to struct page and struct folio"'s recent addition of
private_1to the folio tail: instead addhugetlb_subpool,hugetlb_cgroup,hugetlb_cgroup_rsvd,hugetlb_hwpoisonto a second tail page of the folio: THP has long been using several fields of that tail, so make better use of it for hugetlb too. This is not how a generic folio should be declared in future, but it is an effective transitional way to make use of it....
Quoted 8 lines
include/linux/mm_types.h struct page { · line 270
Quoted 6 lines
include/linux/mm_types.h +1
-1@@ -260,13 +267,16 @@ struct page {* to find how many references there are to this folio. * @memcg_data: Memory Control Group data. * @_flags_1: For large folios, additional page flags. -* @__head: Points to the folio. Do not use. +* @_head_1: Points to the folio. Do not use. Changes to my original patch set look good, this seems to be a cleaner implementation.
Thanks a lot, Sidhartha, I'm glad to hear that it works for you too.
I expect that it will be done differently in the future: maybe generalizing the additional fields to further "private"s as you did, letting different subsystems accessorize them differently; or removing them completely from struct folio, letting subsystems declare their own struct folio containers. I don't know how that will end up, but this for now seems good and clear.
Quoted 1 line
Should the usage of
page_1andpage_2also be documented here?
Quoted 8 lines
You must have something interesting in mind to document about them, but I cannot guess what! They are for field alignment, not for use. (
page_2to help when/if someone needs to add another pageful.)Do you mean that I should copy the
/* private: the union with struct page is transitional */comment from above the original "struct page page;" line I copied? Or give all three of them a few underscores to imply not for use?
I think the underscores with a comment about not for use could be helpful.
Thanks,
Sidhartha Kumar
Quoted 2 lines
Thanks,
Hugh
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
Quoted 7 lines · Sidhartha Kumar
Quoted 6 lines · Hugh Dickins
Quoted 2 lines
Should the usage of
page_1andpage_2also be documented here?You must have something interesting in mind to document about them, but I cannot guess what! They are for field alignment, not for use. (
page_2to help when/if someone needs to add another pageful.)
Quoted 6 lines
Quoted 4 lines
Do you mean that I should copy the
/* private: the union with struct page is transitional */comment from above the original "struct page page;" line I copied? Or give all three of them a few underscores to imply not for use?
I think the underscores with a comment about not for use could be helpful.
I've given them two underscores (but not to the original "struct page page", since a build showed that used as "page" elsewhere, not just for alignment).
I'm sorry, but I've not given them any comment: I don't think they belong in the commented fields section (_flags_1 etc), "page" is not there; and I'm, let's be honest, terrified of dabbling in this kerneldoc area - feel very fortunate to have escaped attack by a robot for my additions so far. I'll leave adding comment to you or other cognoscenti.
Hugh
PATCH 1/3 mm,hugetlb: use folio fields in second tail page: fix
Per review comment from Sidhartha: prefix folio's page_1 and page_2 with double underscore, to underscore that they are fillers for alignment rather than directly usable members of the union (whereas the first "struct page page" is important for folio<->page conversions).
Per review comment from Kirill: give folio's _flags_2 and _head_2 a line of documentation each, though both of them "Do not use" (I think _flags_1 should be enough for now, and shouldn't recommend spilling to _flags_2).
--- include/linux/mm_types.h | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
include/linux/mm_types.h +4 -2
@@ -275,6 +275,8 @@ struct page {* @_subpages_mapcount: Do not use directly, call folio_mapcount(). * @_pincount: Do not use directly, call folio_maybe_dma_pinned(). * @_folio_nr_pages: Do not use directly, call folio_nr_pages(). +* @_flags_2: For alignment. Do not use. +* @_head_2: Points to the folio. Do not use. * @_hugetlb_subpool: Do not use directly, use accessor in hugetlb.h. * @_hugetlb_cgroup: Do not use directly, use accessor in hugetlb_cgroup.h. * @_hugetlb_cgroup_rsvd: Do not use directly, use accessor in hugetlb_cgroup.h.
@@ -330,7 +332,7 @@ struct folio {unsigned int _folio_nr_pages;#endif }; -struct page page_1; +struct page __page_1; }; union { struct {
@@ -341,7 +343,7 @@ struct folio {void *_hugetlb_cgroup_rsvd;void *_hugetlb_hwpoison; }; -struct page page_2; +struct page __page_2; }; };
Signature · 1 line
2.35.3
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
In reply to Hugh Dickinsinclude/linux/mm_types.h struct page { · line 269
Quoted 12 lines · Hugh Dickins
include/linux/mm_types.h +1
-2@@ -260,13 +267,16 @@ struct page {* to find how many references there are to this folio. * @memcg_data: Memory Control Group data. * @_flags_1: For large folios, additional page flags. -* @__head: Points to the folio. Do not use. +* @_head_1: Points to the folio. Do not use. * @_folio_dtor: Which destructor to use for this folio. * @_folio_order: Do not use directly, call folio_order(). * @_total_mapcount: Do not use directly, call folio_entire_mapcount(). * @_pincount: Do not use directly, call folio_maybe_dma_pinned(). * @_folio_nr_pages: Do not use directly, call folio_nr_pages(). -* @_private_1: Do not use directly, call folio_get_private_1().
Looks like it misses
+ * @_flags_2: For large folios, additional page flags.
+ * @_head_2: Points to the folio. Do not use.
to match the first tail page documentation.
Otherwise the patch looks good to me:
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 1/3] mm,hugetlb: use folio fields in second tail page
Quoted 16 lines · Kirill A. Shutemov
include/linux/mm_types.h struct page { · line 269
Quoted 12 lines · Hugh Dickins
include/linux/mm_types.h +1
-2@@ -260,13 +267,16 @@ struct page {* to find how many references there are to this folio. * @memcg_data: Memory Control Group data. * @_flags_1: For large folios, additional page flags. -* @__head: Points to the folio. Do not use. +* @_head_1: Points to the folio. Do not use. * @_folio_dtor: Which destructor to use for this folio. * @_folio_order: Do not use directly, call folio_order(). * @_total_mapcount: Do not use directly, call folio_entire_mapcount(). * @_pincount: Do not use directly, call folio_maybe_dma_pinned(). * @_folio_nr_pages: Do not use directly, call folio_nr_pages(). -* @_private_1: Do not use directly, call folio_get_private_1(). Looks like it misses
Quoted 8 lines
+ * @_flags_2: For large folios, additional page flags.
+ * @_head_2: Points to the folio. Do not use.to match the first tail page documentation.
Otherwise the patch looks good to me:
Many thanks for all your encouragement and reviews, Kirill.
Okay, I've added a couple of lines on those fields; but did not want to recommend the _flags_2 field for use (by the time we run out in _flags_1, I hope all this will be gone or look different).
I'm sending an incremental fix, once I've responded to Sidhartha.
Hugh
PATCH 2/3 mm,thp,rmap: simplify compound page mapcount handling
In reply to Hugh DickinsCompound page (folio) mapcount calculations have been different for anon and file (or shmem) THPs, and involved the obscure PageDoubleMap flag. And each huge mapping and unmapping of a file (or shmem) THP involved atomically incrementing and decrementing the mapcount of every subpage of that huge page, dirtying many struct page cachelines.
Add subpages_mapcount field to the struct folio and first tail page, so that the total of subpage mapcounts is available in one place near the head: then page_mapcount() and total_mapcount() and page_mapped(), and their folio equivalents, are so quick that anon and file and hugetlb don't need to be optimized differently. Delete the unloved PageDoubleMap.
page_add and page_remove rmap functions must now maintain the subpages_mapcount as well as the subpage _mapcount, when dealing with pte mappings of huge pages; and correct maintenance of NR_ANON_MAPPED and NR_FILE_MAPPED statistics still needs reading through the subpages, using nr_subpages_unmapped() - but only when first or last pmd mapping finds subpages_mapcount raised (double-map case, not the common case).
But are those counts (used to decide when to split an anon THP, and in vmscan's pagecache_reclaimable heuristic) correctly maintained? Not quite: since page_remove_rmap() (and also split_huge_pmd()) is often called without page lock, there can be races when a subpage pte mapcount 0<->1 while compound pmd mapcount 0<->1 is scanning - races which the previous implementation had prevented. The statistics might become inaccurate, and even drift down until they underflow through 0. That is not good enough, but is better dealt with in a followup patch.
Update a few comments on first and second tail page overlaid fields. hugepage_add_new_anon_rmap() has to "increment" compound_mapcount, but subpages_mapcount and compound_pincount are already correctly at 0, so delete its reinitialization of compound_pincount.
A simple 100 X munmap(mmap(2GB, MAP_SHARED|MAP_POPULATE, tmpfs), 2GB) took 18 seconds on small pages, and used to take 1 second on huge pages, but now takes 119 milliseconds on huge pages. Mapping by pmds a second time used to take 860ms and now takes 92ms; mapping by pmds after mapping by ptes (when the scan is needed) used to take 870ms and now takes 495ms. But there might be some benchmarks which would show a slowdown, because tail struct pages now fall out of cache until final freeing checks them.
--- Documentation/mm/transhuge.rst | 18 ----- include/linux/mm.h | 85 ++++++++++++++------ include/linux/mm_types.h | 21 ++++- include/linux/page-flags.h | 21 ----- include/linux/rmap.h | 2 + mm/debug.c | 5 +- mm/folio-compat.c | 6 -- mm/huge_memory.c | 36 ++------- mm/hugetlb.c | 2 + mm/khugepaged.c | 11 +-- mm/page_alloc.c | 27 ++++--- mm/rmap.c | 142 +++++++++++++++++++-------------- mm/util.c | 79 ------------------ 13 files changed, 194 insertions(+), 261 deletions(-)
Documentation/mm/transhuge.rst +0 -18
@@ -125,24 +125,6 @@ pages: ->_mapcount of all sub-pages in order to have race-free detection of last unmap of subpages. -PageDoubleMap() indicates that the page is *possibly* mapped with PTEs. - -For anonymous pages, PageDoubleMap() also indicates ->_mapcount in all -subpages is offset up by one. This additional reference is required to -get race-free detection of unmap of subpages when we have them mapped with -both PMDs and PTEs. - -This optimization is required to lower the overhead of per-subpage mapcount -tracking. The alternative is to alter ->_mapcount in all subpages on each -map/unmap of the whole compound page. - -For anonymous pages, we set PG_double_map when a PMD of the page is split -for the first time, but still have a PMD mapping. The additional references -go away with the last compound_mapcount. - -File pages get PG_double_map set on the first map of the page with PTE and -goes away when the page gets evicted from the page cache. - split_huge_page internally has to distribute the refcounts in the head page to the tail pages before clearing all PG_head/tail bits from the page structures. It can be done easily for refcounts taken by page table
include/linux/mm.h +62 -23
127 lines not on this page · raw message
include/linux/mm_types.h +18 -3
@@ -142,6 +142,7 @@ struct page {unsigned char compound_dtor;unsigned char compound_order;atomic_t compound_mapcount; +atomic_t subpages_mapcount;atomic_t compound_pincount;#ifdef CONFIG_64BIT unsigned int compound_nr;/* 1 << compound_order */
@@ -270,7 +271,8 @@ struct page {* @_head_1: Points to the folio. Do not use. * @_folio_dtor: Which destructor to use for this folio. * @_folio_order: Do not use directly, call folio_order(). -* @_total_mapcount: Do not use directly, call folio_entire_mapcount(). +* @_compound_mapcount: Do not use directly, call folio_entire_mapcount(). +* @_subpages_mapcount: Do not use directly, call folio_mapcount(). * @_pincount: Do not use directly, call folio_maybe_dma_pinned(). * @_folio_nr_pages: Do not use directly, call folio_nr_pages(). * @_hugetlb_subpool: Do not use directly, use accessor in hugetlb.h.
@@ -321,7 +323,8 @@ struct folio {unsigned long _head_1;unsigned char _folio_dtor;unsigned char _folio_order; -atomic_t _total_mapcount; +atomic_t _compound_mapcount; +atomic_t _subpages_mapcount;atomic_t _pincount;#ifdef CONFIG_64BIT unsigned int _folio_nr_pages;
@@ -363,7 +366,8 @@ FOLIO_MATCH(flags, _flags_1);FOLIO_MATCH (compound_head, _head_1);FOLIO_MATCH (compound_dtor, _folio_dtor);FOLIO_MATCH (compound_order, _folio_order); -FOLIO_MATCH (compound_mapcount, _total_mapcount); +FOLIO_MATCH (compound_mapcount, _compound_mapcount); +FOLIO_MATCH (subpages_mapcount, _subpages_mapcount);FOLIO_MATCH (compound_pincount, _pincount);#ifdef CONFIG_64BIT FOLIO_MATCH (compound_nr, _folio_nr_pages);
@@ -386,11 +390,22 @@ static inline atomic_t *folio_mapcount_ptr(struct folio *folio)return &tail->compound_mapcount; } +static inline atomic_t *folio_subpages_mapcount_ptr (struct folio *folio) +{ +struct page *tail = &folio->page +1 ; +return &tail->subpages_mapcount; +} +static inline atomic_t *compound_mapcount_ptr (struct page *page) {return &page[1 ].compound_mapcount; } +static inline atomic_t *subpages_mapcount_ptr (struct page *page) +{ +return &page[1 ].subpages_mapcount; +} +static inline atomic_t *compound_pincount_ptr (struct page *page) {return &page[1 ].compound_pincount;
include/linux/page-flags.h +0 -21
@@ -176,9 +176,6 @@ enum pageflags {/* SLOB */ PG_slob_free = PG_private, -/* Compound pages. Stored in first tail page's flags */ - PG_double_map = PG_workingset, - #ifdef CONFIG_MEMORY_FAILURE/* * Compound pages. Stored in first tail page's flags.
@@ -874,29 +871,11 @@ static inline int PageTransTail(struct page *page) {return PageTail (page); } - -/* -* PageDoubleMap indicates that the compound page is mapped with PTEs as well -* as PMDs. -* -* This is required for optimization of rmap operations for THP: we can postpone -* per small page mapcount accounting (and its overhead from atomic operations) -* until the first PMD split. -* -* For the page PageDoubleMap means ->_mapcount in all sub-pages is offset up -* by one. This reference will go away with last compound_mapcount. -* -* See also __split_huge_pmd_locked() and page_remove_anon_compound_rmap(). -*/ -PAGEFLAG(DoubleMap, double_map, PF_SECOND) - TESTSCFLAG(DoubleMap, double_map, PF_SECOND)#else TESTPAGEFLAG_FALSE(TransHuge, transhuge) TESTPAGEFLAG_FALSE(TransCompound, transcompound) TESTPAGEFLAG_FALSE(TransCompoundMap, transcompoundmap) TESTPAGEFLAG_FALSE(TransTail, transtail) -PAGEFLAG_FALSE(DoubleMap, double_map) - TESTSCFLAG_FALSE(DoubleMap, double_map)#endif #if defined(CONFIG_MEMORY_FAILURE ) && defined(CONFIG_TRANSPARENT_HUGEPAGE )
include/linux/rmap.h +2 -0
@@ -206,6 +206,8 @@ void hugepage_add_new_anon_rmap(struct page *, struct vm_area_struct *,static inline void __page_dup_rmap (struct page *page,bool compound) { +if (!compound &&PageCompound (page)) +atomic_inc (subpages_mapcount_ptr (compound_head (page)));atomic_inc (compound ?compound_mapcount_ptr (page) : &page->_mapcount); }
mm/debug.c +3 -2
@@ -94,9 +94,10 @@ static void __dump_page(struct page *page) page,page_ref_count (head), mapcount, mapping, page_to_pgoff(page), page_to_pfn(page));if (compound) { -pr_warn ("head:%p order:%u compound_mapcount:%d compound_pincount:%d\n" , +pr_warn ("head:%p order:%u compound_mapcount:%d subpages_mapcount:%d compound_pincount:%d\n" , head,compound_order (head), -folio_entire_mapcount (folio), +head_compound_mapcount (head), +head_subpages_mapcount (head),head_compound_pincount (head)); }
mm/folio-compat.c +0 -6
@@ -39,12 +39,6 @@ void wait_for_stable_page(struct page *page) }EXPORT_SYMBOL_GPL (wait_for_stable_page); -bool page_mapped (struct page *page) -{ -return folio_mapped (page_folio (page)); -} -EXPORT_SYMBOL (page_mapped); -void mark_page_accessed (struct page *page) {folio_mark_accessed (page_folio (page));
mm/huge_memory.c +8 -28
@@ -2093,6 +2093,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,VM_BUG_ON_PAGE (!page_count (page), page);page_ref_add (page,HPAGE_PMD_NR -1 ); +atomic_add (HPAGE_PMD_NR ,subpages_mapcount_ptr (page));/* * Without "freeze", we'll simply split the PMD, propagating the
@@ -2173,33 +2174,8 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,pte_unmap (pte); } -if (!pmd_migration) { -/* -* Set PG_double_map before dropping compound_mapcount to avoid -* false-negative page_mapped(). -*/ -if (compound_mapcount (page) >1 && - !TestSetPageDoubleMap (page)) { -for (i =0 ; i <HPAGE_PMD_NR ; i++) -atomic_inc (&page[i]._mapcount); - } - -lock_page_memcg (page); -if (atomic_add_negative (-1 ,compound_mapcount_ptr (page))) { -/* Last compound_mapcount is gone. */ -__mod_lruvec_page_state (page,NR_ANON_THPS , - -HPAGE_PMD_NR ); -if (TestClearPageDoubleMap (page)) { -/* No need in mapcount reference anymore */ -for (i =0 ; i <HPAGE_PMD_NR ; i++) -atomic_dec (&page[i]._mapcount); - } - } -unlock_page_memcg (page); - -/* Above is effectively page_remove_rmap(page, vma, true) */ -munlock_vma_page (page, vma, true); - } +if (!pmd_migration) +page_remove_rmap (page, vma, true);smp_wmb ();/* make pte visible before pmd */ pmd_populate (mm, pmd, pgtable);
@@ -2401,7 +2377,7 @@ static void __split_huge_page_tail(struct page *head, int tail, (1L << PG_dirty) | LRU_GEN_MASK | LRU_REFS_MASK)); -/* ->mapping in first tail page is compound_mapcount */ +/* ->mapping in first and second tail page is replaced by other uses */ VM_BUG_ON_PAGE (tail >2 && page_tail->mapping !=TAIL_MAPPING , page_tail); page_tail->mapping = head->mapping;
@@ -2411,6 +2387,10 @@ static void __split_huge_page_tail(struct page *head, int tail,* page->private should not be set in tail pages with the exception * of swap cache pages that store the swp_entry_t in tail pages. * Fix up and warn once if private is unexpectedly set. +* +* What of 32-bit systems, on which head[1].compound_pincount overlays +* head[1].private? No problem: THP_SWAP is not enabled on 32-bit, and +* compound_pincount must be 0 for folio_ref_freeze() to have succeeded. */ if (!folio_test_swapcache (page_folio (head))) {VM_WARN_ON_ONCE_PAGE (page_tail->private !=0 , page_tail);
mm/hugetlb.c +2 -0
@@ -1333,6 +1333,7 @@ static void __destroy_compound_gigantic_page(struct page *page,struct page *p;atomic_set (compound_mapcount_ptr (page),0 ); +atomic_set (subpages_mapcount_ptr (page),0 );atomic_set (compound_pincount_ptr (page),0 );for (i =1 ; i < nr_pages; i++) {
@@ -1850,6 +1851,7 @@ static bool __prep_compound_gigantic_page(struct page *page, unsigned int order,set_compound_head (p, page); }atomic_set (compound_mapcount_ptr (page),-1 ); +atomic_set (subpages_mapcount_ptr (page),0 );atomic_set (compound_pincount_ptr (page),0 );return true;
mm/khugepaged.c +2 -9
@@ -1242,15 +1242,8 @@ static int hpage_collapse_scan_pmd(struct mm_struct *mm,/* * Check if the page has any GUP (or other external) pins. * -* Here the check is racy it may see total_mapcount > refcount -* in some cases. -* For example, one process with one forked child process. -* The parent has the PMD split due to MADV_DONTNEED, then -* the child is trying unmap the whole PMD, but khugepaged -* may be scanning the parent between the child has -* PageDoubleMap flag cleared and dec the mapcount. So -* khugepaged may see total_mapcount > refcount. -* +* Here the check may be racy: +* it may see total_mapcount > refcount in some cases? * But such case is ephemeral we could always retry collapse * later. However it may report false positive if the page * has excessive GUP pins (i.e. 512). Anyway the same check
mm/page_alloc.c +16 -11
@@ -798,6 +798,7 @@ static void prep_compound_head(struct page *page, unsigned int order)set_compound_page_dtor (page,COMPOUND_PAGE_DTOR );set_compound_order (page, order);atomic_set (compound_mapcount_ptr (page),-1 ); +atomic_set (subpages_mapcount_ptr (page),0 );atomic_set (compound_pincount_ptr (page),0 ); }
@@ -1324,11 +1325,19 @@ static int free_tail_pages_check(struct page *head_page, struct page *page) }switch (page - head_page) {case 1 : -/* the first tail page: ->mapping may be compound_mapcount() */ -if (unlikely (compound_mapcount (page))) { +/* the first tail page: these may be in place of ->mapping */ +if (unlikely (head_compound_mapcount (head_page))) {bad_page (page,"nonzero compound_mapcount" ); goto out; } +if (unlikely (head_subpages_mapcount (head_page))) { +bad_page (page,"nonzero subpages_mapcount" ); + goto out; + } +if (unlikely (head_compound_pincount (head_page))) { +bad_page (page,"nonzero compound_pincount" ); + goto out; + }break ;case 2 :/*
@@ -1433,10 +1442,8 @@ static __always_inline bool free_pages_prepare(struct page *page,VM_BUG_ON_PAGE (compound &&compound_order (page) != order, page); -if (compound) { -ClearPageDoubleMap (page); +if (compound)ClearPageHasHWPoisoned (page); - }for (i =1 ; i < (1 << order); i++) {if (compound) bad +=free_tail_pages_check (page, page + i);
@@ -6871,13 +6878,11 @@ static void __ref memmap_init_compound(struct page *head,set_page_count (page,0 );/* -* The first tail page stores compound_mapcount_ptr() and -* compound_order() and the second tail page stores -* compound_pincount_ptr(). Call prep_compound_head() after -* the first and second tail pages have been initialized to -* not have the data overwritten. +* The first tail page stores important compound page info. +* Call prep_compound_head() after the first tail page has +* been initialized, to not have the data overwritten. */ -if (pfn == head_pfn +2 ) +if (pfn == head_pfn +1 )prep_compound_head (head, order); } }
mm/rmap.c +81 -61
263 lines not on this page · raw message
mm/util.c +0 -79
91 lines not on this page · raw message
Signature · 1 line
2.35.3
Re: [PATCH 2/3] mm,thp,rmap: simplify compound page mapcount handling
Quoted 41 lines · Hugh Dickins
Compound page (folio) mapcount calculations have been different for anon and file (or shmem) THPs, and involved the obscure PageDoubleMap flag. And each huge mapping and unmapping of a file (or shmem) THP involved atomically incrementing and decrementing the mapcount of every subpage of that huge page, dirtying many struct page cachelines.
Add
subpages_mapcountfield to the struct folio and first tail page, so that the total of subpage mapcounts is available in one place near the head: thenpage_mapcount()andtotal_mapcount()andpage_mapped(), and their folio equivalents, are so quick that anon and file and hugetlb don't need to be optimized differently. Delete the unloved PageDoubleMap.
page_addandpage_removermap functions must now maintain thesubpages_mapcountas well as the subpage_mapcount, when dealing with pte mappings of huge pages; and correct maintenance ofNR_ANON_MAPPEDandNR_FILE_MAPPEDstatistics still needs reading through the subpages, usingnr_subpages_unmapped()- but only when first or last pmd mapping findssubpages_mapcountraised (double-map case, not the common case).But are those counts (used to decide when to split an anon THP, and in vmscan's
pagecache_reclaimableheuristic) correctly maintained? Not quite: sincepage_remove_rmap()(and alsosplit_huge_pmd()) is often called without page lock, there can be races when a subpage pte mapcount 0<->1 while compound pmd mapcount 0<->1 is scanning - races which the previous implementation had prevented. The statistics might become inaccurate, and even drift down until they underflow through 0. That is not good enough, but is better dealt with in a followup patch.Update a few comments on first and second tail page overlaid fields.
hugepage_add_new_anon_rmap()has to "increment"compound_mapcount, butsubpages_mapcountandcompound_pincountare already correctly at 0, so delete its reinitialization ofcompound_pincount.A simple 100 X
munmap(mmap(2GB, MAP_SHARED|MAP_POPULATE, tmpfs), 2GB)took 18 seconds on small pages, and used to take 1 second on huge pages, but now takes 119 milliseconds on huge pages. Mapping by pmds a second time used to take 860ms and now takes 92ms; mapping by pmds after mapping by ptes (when the scan is needed) used to take 870ms and now takes 495ms. But there might be some benchmarks which would show a slowdown, because tail struct pages now fall out of cache until final freeing checks them.
Quoted 1 line
Signed-off-by Hugh Dickins <[email protected]>
Thanks for doing this!
And sorry again for PageDoubleMap() :/
Minor nitpick and a question below.
Quoted 15 lines
include/linux/mm.h +5
-4@@ -829,12 +829,20 @@ static inline int folio_entire_mapcount(struct folio *folio)/* * Mapcount of compound page as a whole, does not include mapped sub-pages. -* -* Must be called only for compound pages. +* Must be called only on head of compound page. */ -static inline int compound_mapcount (struct page *page) +static inline int head_compound_mapcount (struct page *head) { -return folio_entire_mapcount (page_folio (page)); +return atomic_read (compound_mapcount_ptr (head)) +1 ; +} +
include/linux/mm.h static inline int folio_entire_mapcount(struct folio *folio) · line 848
Quoted 10 lines
include/linux/mm.h +7
-0+/* +* Sum of mapcounts of sub-pages, does not include compound mapcount. +* Must be called only on head of compound page. +*/ +static inline int head_subpages_mapcount (struct page *head) +{ +return atomic_read (subpages_mapcount_ptr (head)); }/*
Any particular reason these two do not take struct folio as an input? It would guarantee that it is non-tail page. It will not guarantee large-folio, but it is something.
mm/rmap.c void page_add_new_anon_rmap(struct page *page, · line 1269
Quoted 6 lines
mm/rmap.c +0
-2@@ -1265,8 +1288,6 @@ void page_add_new_anon_rmap(struct page *page,VM_BUG_ON_PAGE (!PageTransHuge (page), page);/* increment count (starts at -1) */ atomic_set (compound_mapcount_ptr (page),0 ); -atomic_set (compound_pincount_ptr (page),0 ); -
It has to be initialized to 0 on allocation, right?
Quoted 3 lines
mm/rmap.c +0
-0__mod_lruvec_page_state (page,NR_ANON_THPS , nr); }else {/* increment count (starts at -1) */
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 2/3] mm,thp,rmap: simplify compound page mapcount handling
Quoted 5 lines · Kirill A. Shutemov
On Wed, Nov 02, 2022 at 06:51:38PM -0700, Hugh Dickins wrote:
Thanks for doing this!
Thanks!
Quoted 2 lines
And sorry again for
PageDoubleMap():/
It did serve a real purpose, but I always found it hard to live with, and I'm glad that you're happy it's gone too :)
Quoted 27 lines
Minor nitpick and a question below.
Quoted 24 lines
include/linux/mm.h +12
-4@@ -829,12 +829,20 @@ static inline int folio_entire_mapcount(struct folio *folio)/* * Mapcount of compound page as a whole, does not include mapped sub-pages. -* -* Must be called only for compound pages. +* Must be called only on head of compound page. */ -static inline int compound_mapcount (struct page *page) +static inline int head_compound_mapcount (struct page *head) { -return folio_entire_mapcount (page_folio (page)); +return atomic_read (compound_mapcount_ptr (head)) +1 ; +} + +/* +* Sum of mapcounts of sub-pages, does not include compound mapcount. +* Must be called only on head of compound page. +*/ +static inline int head_subpages_mapcount (struct page *head) +{ +return atomic_read (subpages_mapcount_ptr (head)); }
Quoted 5 lines
Review static inline int folio_entire_mapcount(struct folio *folio) · line 848
Quoted 1 line
(quoted diff) +0
-0/*Any particular reason these two do not take struct folio as an input? It would guarantee that it is non-tail page. It will not guarantee large-folio, but it is something.
The actual reason is that I first did this work in a pre-folio tree; and even now I am much more at ease with compound pages than folios.
But when I looked to see if I ought to change them, found that the only uses are below in this header file, or in __dump_page() or in free_tail_pages_check() - low-level functions, page-oriented and obviously on head. So I wasn't tempted to change them at all.
Quoted 9 lines
mm/rmap.c void page_add_new_anon_rmap(struct page *page, · line 1269
Quoted 7 lines
mm/rmap.c +0
-2@@ -1265,8 +1288,6 @@ void page_add_new_anon_rmap(struct page *page,VM_BUG_ON_PAGE (!PageTransHuge (page), page);/* increment count (starts at -1) */ atomic_set (compound_mapcount_ptr (page),0 ); -atomic_set (compound_pincount_ptr (page),0 ); -It has to be initialized to 0 on allocation, right?
That's right. I was going to say that I'd commented on this in the commit message, but no, it looks like I only commented on the instance in hugepage_add_new_new_anon_rmap() (and added the "increment" comment line from here to there).
I visited both those functions to add a matching subpages_mapcount initialization; then realized that the pincount addition had missed the point, initialization to 0 has already been done, and the compound_mapcount line is about incrementing from -1 to 0, not about initializing.
There are similar places in mm/hugetlb.c, where I did add the subpages_mapcount initialization to the compound_pincount and compound_mapcount initializations: that's because I'm on shaky ground with hugetlb page lifecycle, and not so sure of their status there.
Hugh
PATCH 3/3 mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
In reply to Hugh DickinsFix the races in maintaining compound_mapcount, subpages_mapcount and subpage _mapcount by using PG_locked in the first tail of any compound page for a bit_spin_lock() on such modifications; skipping the usual atomic operations on those fields in this case.
Bring page_remove_file_rmap() and page_remove_anon_compound_rmap() back into page_remove_rmap() itself. Rearrange page_add_anon_rmap() and page_add_file_rmap() and page_remove_rmap() to follow the same "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern (with a PageTransHuge in the compound test, like before, to avoid BUG_ONs and optimize away that block when THP is not configured). Move all the stats updates outside, after the bit_spin_locked section, so that it is sure to be a leaf lock.
Add page_dup_compound_rmap() to manage compound locking versus atomics in sync with the rest. In particular, hugetlb pages are still using the atomics: to avoid unnecessary interference there, and because they never have subpage mappings; but this exception can easily be changed. Conveniently, page_dup_compound_rmap() turns out to suit an anon THP's __split_huge_pmd_locked() too.
bit_spin_lock() is not popular with PREEMPT_RT folks: but PREEMPT_RT sensibly excludes TRANSPARENT_HUGEPAGE already, so its only exposure is to the non-hugetlb non-THP pte-mapped compound pages (with large folios being currently dependent on TRANSPARENT_HUGEPAGE). There is never any scan of subpages in this case; but we have chosen to use PageCompound tests rather than PageTransCompound tests to gate the use of lock_compound_mapcounts(), so that page_mapped() is correct on all compound pages, whether or not TRANSPARENT_HUGEPAGE is enabled:
could that be a problem for PREEMPT_RT, when there is contention on the lock - under heavy concurrent forking for example? If so, then it can be turned into a sleeping lock (like folio_lock()) when PREEMPT_RT.
A simple 100 X munmap(mmap(2GB, MAP_SHARED|MAP_POPULATE, tmpfs), 2GB) took 18 seconds on small pages, and used to take 1 second on huge pages, but now takes 115 milliseconds on huge pages. Mapping by pmds a second time used to take 860ms and now takes 86ms; mapping by pmds after mapping by ptes (when the scan is needed) used to take 870ms and now takes 495ms. Mapping huge pages by ptes is largely unaffected but variable: between 5% faster and 5% slower in what I've recorded. Contention on the lock is likely to behave worse than contention on the atomics behaved.
--- Documentation/mm/transhuge.rst | 16 +- include/linux/rmap.h | 14 +- mm/huge_memory.c | 3 +- mm/rmap.c | 333 +++++++++++++++++++-------------- 4 files changed, 204 insertions(+), 162 deletions(-)
Documentation/mm/transhuge.rst +9 -7
@@ -117,13 +117,15 @@ pages: - ->_refcount in tail pages is always zero: get_page_unless_zero() never succeeds on tail pages. - - map/unmap of the pages with PTE entry increment/decrement ->_mapcount - on relevant sub-page of the compound page. - - - map/unmap of the whole compound page is accounted for in compound_mapcount - (stored in first tail page). For file huge pages, we also increment - ->_mapcount of all sub-pages in order to have race-free detection of - last unmap of subpages. + - map/unmap of PMD entry for the whole compound page increment/decrement + ->compound_mapcount, stored in the first tail page of the compound page. + + - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount + on relevant sub-page of the compound page, and also increment/decrement + ->subpages_mapcount, stored in first tail page of the compound page. + In order to have race-free accounting of sub-pages mapped, changes to + sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are + are all locked by bit_spin_lock of PG_locked in the first tail ->flags. split_huge_page internally has to distribute the refcounts in the head page to the tail pages before clearing all PG_head/tail bits from the page
include/linux/rmap.h +6 -8
@@ -204,16 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -static inline void __page_dup_rmap (struct page *page,bool compound) -{ -if (!compound &&PageCompound (page)) -atomic_inc (subpages_mapcount_ptr (compound_head (page))); -atomic_inc (compound ?compound_mapcount_ptr (page) : &page->_mapcount); -} +void page_dup_compound_rmap (struct page *page,bool compound);static inline void page_dup_file_rmap (struct page *page,bool compound) { -__page_dup_rmap (page, compound); +if (PageCompound (page)) +page_dup_compound_rmap (page, compound); +else +atomic_inc (&page->_mapcount); }/**
@@ -262,7 +260,7 @@ static inline int page_try_dup_anon_rmap(struct page *page, bool compound,* the page R/O into both processes. */ dup: -__page_dup_rmap (page, compound); +page_dup_file_rmap (page, compound);return 0 ; }
mm/huge_memory.c +1 -2
@@ -2093,7 +2093,6 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,VM_BUG_ON_PAGE (!page_count (page), page);page_ref_add (page,HPAGE_PMD_NR -1 ); -atomic_add (HPAGE_PMD_NR ,subpages_mapcount_ptr (page));/* * Without "freeze", we'll simply split the PMD, propagating the
@@ -2170,7 +2169,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry);if (!pmd_migration) -atomic_inc (&page[i]._mapcount); +page_dup_compound_rmap (page + i, false);pte_unmap (pte); }
mm/rmap.c +188 -145
421 lines not on this page · raw message
Signature · 1 line
2.35.3
kernel test robot
build bot[lkp] [+360 bytes kernel size regression] [i386-tinyconfig] [a3cbd790ac] mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
FYI, we noticed a +360 bytes kernel size regression due to commit:
FYI, we noticed a +360 bytes kernel size regression due to commit:
commit: a3cbd790ac6e9d8f6d63731647a8123d0fdc69a8 (mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts)
url: https://github.com/intel-lab-lkp/linux/commits/Hugh-Dickins/mm-huge-rmap-unify-and-speed-up-compound-mapcounts/20221103-095502
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/lkml/[email protected]
patch subject: [PATCH 3/3] mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
Details as below (size data is obtained by nm --size-sort vmlinux):
74c6c283: mm,thp,rmap: simplify compound page mapcount handlinga3cbd790: mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
+--------------------------------+----------+----------+-------+ | symbol | 74c6c283 | a3cbd790 | delta | +--------------------------------+----------+----------+-------+ | bzImage | 491584 | 491712 | 128 | | nm.T.page_add_anon_rmap | 100 | 209 | 109 | | nm.T.page_add_file_rmap | 39 | 143 | 104 | | nm.T.page_dup_compound_rmap | 0 | 69 | 69 | | nm.T.page_remove_rmap | 87 | 151 | 64 | | nm.t.page_dup_file_rmap | 0 | 28 | 28 | | nm.t.lock_compound_mapcounts | 0 | 13 | 13 | | nm.t.unlock_compound_mapcounts | 0 | 13 | 13 | | nm.t.__page_dup_rmap | 40 | 0 | -40 | +--------------------------------+----------+----------+-------+
Thanks
Re: [lkp] [+360 bytes kernel size regression] [i386-tinyconfig] [a3cbd790ac] mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
Quoted 15 lines · kernel test robot
FYI, we noticed a +360 bytes kernel size regression due to commit:
commit:
a3cbd790ac6e9d8f6d63731647a8123d0fdc69a8(mm,thp,rmap:lock_compound_mapcounts()on THP mapcounts)
url: https://github.com/intel-lab-lkp/linux/commits/Hugh-Dickins/mm-huge-rmap-unify-and-speed-up-compound-mapcounts/20221103-095502
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/lkml/[email protected]
patch subject: [PATCH 3/3] mm,thp,rmap:lock_compound_mapcounts()on THP mapcountsDetails as below (size data is obtained by
nm --size-sort vmlinux):
74c6c283: mm,thp,rmap: simplify compound page mapcount handlinga3cbd790: mm,thp,rmap:lock_compound_mapcounts()on THP mapcounts
Quoted 13 lines
+--------------------------------+----------+----------+-------+ | symbol | 74c6c283 | a3cbd790 | delta | +--------------------------------+----------+----------+-------+ | bzImage | 491584 | 491712 | 128 | | nm.T.page_add_anon_rmap | 100 | 209 | 109 | | nm.T.page_add_file_rmap | 39 | 143 | 104 | | nm.T.page_dup_compound_rmap | 0 | 69 | 69 | | nm.T.page_remove_rmap | 87 | 151 | 64 | | nm.t.page_dup_file_rmap | 0 | 28 | 28 | | nm.t.lock_compound_mapcounts | 0 | 13 | 13 | | nm.t.unlock_compound_mapcounts | 0 | 13 | 13 | | nm.t.__page_dup_rmap | 40 | 0 | -40 | +--------------------------------+----------+----------+-------+
Thanks for the feedback. But I think you'll find that patch 2/3 gave a nice little negative size delta over patch 1/3 and baseline:
it's not surprising if patch 3/3 then adds some back. With my own configs, I had found that the total text size ended up exactly the same, or 80 bytes less, after the series; but 130 bytes less midway.
Ah, i386-tinyconfig: I wonder if that does not enable THP, and suffers a little from doing more work on PageCompound now. +360 is more than I'd expect, but I won't worry about it, until the humans start complaining.
Hugh
Re: [PATCH 3/3] mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
In reply to Hugh DickinsQuoted 42 lines · Hugh Dickins
Fix the races in maintaining
compound_mapcount,subpages_mapcountand subpage_mapcountby usingPG_lockedin the first tail of any compound page for abit_spin_lock()on such modifications; skipping the usual atomic operations on those fields in this case.Bring
page_remove_file_rmap()andpage_remove_anon_compound_rmap()back intopage_remove_rmap()itself. Rearrangepage_add_anon_rmap()andpage_add_file_rmap()andpage_remove_rmap()to follow the same "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern (with a PageTransHuge in the compound test, like before, to avoidBUG_ONsand optimize away that block when THP is not configured). Move all the stats updates outside, after thebit_spin_lockedsection, so that it is sure to be a leaf lock.Add
page_dup_compound_rmap()to manage compound locking versus atomics in sync with the rest. In particular, hugetlb pages are still using the atomics: to avoid unnecessary interference there, and because they never have subpage mappings; but this exception can easily be changed. Conveniently,page_dup_compound_rmap()turns out to suit an anon THP's__split_huge_pmd_locked()too.
bit_spin_lock()is not popular withPREEMPT_RTfolks: butPREEMPT_RTsensibly excludesTRANSPARENT_HUGEPAGEalready, so its only exposure is to the non-hugetlb non-THP pte-mapped compound pages (with large folios being currently dependent onTRANSPARENT_HUGEPAGE). There is never any scan of subpages in this case; but we have chosen to use PageCompound tests rather than PageTransCompound tests to gate the use oflock_compound_mapcounts(), so thatpage_mapped()is correct on all compound pages, whether or notTRANSPARENT_HUGEPAGEis enabled:
could that be a problem forPREEMPT_RT, when there is contention on the lock - under heavy concurrent forking for example? If so, then it can be turned into a sleeping lock (likefolio_lock()) whenPREEMPT_RT.A simple 100 X
munmap(mmap(2GB, MAP_SHARED|MAP_POPULATE, tmpfs), 2GB)took 18 seconds on small pages, and used to take 1 second on huge pages, but now takes 115 milliseconds on huge pages. Mapping by pmds a second time used to take 860ms and now takes 86ms; mapping by pmds after mapping by ptes (when the scan is needed) used to take 870ms and now takes 495ms. Mapping huge pages by ptes is largely unaffected but variable: between 5% faster and 5% slower in what I've recorded. Contention on the lock is likely to behave worse than contention on the atomics behaved.
Quoted 1 line
Signed-off-by Hugh Dickins <[email protected]>
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 3/3] mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts
Quoted 43 lines · Kirill A. Shutemov
Quoted 42 lines · Hugh Dickins
Fix the races in maintaining
compound_mapcount,subpages_mapcountand subpage_mapcountby usingPG_lockedin the first tail of any compound page for abit_spin_lock()on such modifications; skipping the usual atomic operations on those fields in this case.Bring
page_remove_file_rmap()andpage_remove_anon_compound_rmap()back intopage_remove_rmap()itself. Rearrangepage_add_anon_rmap()andpage_add_file_rmap()andpage_remove_rmap()to follow the same "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern (with a PageTransHuge in the compound test, like before, to avoidBUG_ONsand optimize away that block when THP is not configured). Move all the stats updates outside, after thebit_spin_lockedsection, so that it is sure to be a leaf lock.Add
page_dup_compound_rmap()to manage compound locking versus atomics in sync with the rest. In particular, hugetlb pages are still using the atomics: to avoid unnecessary interference there, and because they never have subpage mappings; but this exception can easily be changed. Conveniently,page_dup_compound_rmap()turns out to suit an anon THP's__split_huge_pmd_locked()too.
bit_spin_lock()is not popular withPREEMPT_RTfolks: butPREEMPT_RTsensibly excludesTRANSPARENT_HUGEPAGEalready, so its only exposure is to the non-hugetlb non-THP pte-mapped compound pages (with large folios being currently dependent onTRANSPARENT_HUGEPAGE). There is never any scan of subpages in this case; but we have chosen to use PageCompound tests rather than PageTransCompound tests to gate the use oflock_compound_mapcounts(), so thatpage_mapped()is correct on all compound pages, whether or notTRANSPARENT_HUGEPAGEis enabled:
could that be a problem forPREEMPT_RT, when there is contention on the lock - under heavy concurrent forking for example? If so, then it can be turned into a sleeping lock (likefolio_lock()) whenPREEMPT_RT.A simple 100 X
munmap(mmap(2GB, MAP_SHARED|MAP_POPULATE, tmpfs), 2GB)took 18 seconds on small pages, and used to take 1 second on huge pages, but now takes 115 milliseconds on huge pages. Mapping by pmds a second time used to take 860ms and now takes 86ms; mapping by pmds after mapping by ptes (when the scan is needed) used to take 870ms and now takes 495ms. Mapping huge pages by ptes is largely unaffected but variable: between 5% faster and 5% slower in what I've recorded. Contention on the lock is likely to behave worse than contention on the atomics behaved.
Quoted 3 lines
Quoted 1 line
Signed-off-by Hugh Dickins <[email protected]>
Thanks, Kirill; and there's a 4/3 posted to change around that "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" ordering, which Linus hated.
But this might be a good place to mention, that Linus (I'd sent private mail to sort out mm-unstable instabilities in a hurry, and discussion ensued from there) does not like this patch very much, and has a good idea for improving it, but has let us move forward with this for now.
His idea is for subpages_mapcount not to count all the ptes of subpages, but to count all the subpages which have ptes (or I think that's one way of saying it, but not how he said it): count what the stats need counted.
I was sceptical at first, because that was indeed something I had tried at one point, but decided against. I am hoping that it will turn out just to be my prejudice: that I embarked on this job, in large part, to get rid of the scan lurking inside total_mapcount(). And Linus's idea would appear to bring back the unlocked scan in total_mapcount():
but remove all the locked scans in page_add/remove_rmap() - which, setting aside my prejudice, sounds like a big improvement (in the double-mapped case; common cases unchanged).
I was not enthusiastic, in that discussion several days ago, but got quite excited once I had a moment to consider (but I've not told him so until now). I'll try to pursue it this weekend: maybe I'll rediscover a good reason why it had to be abandoned, but let's hope it works out.
Anyway, what's in mm-unstable is good, and an improvement over the old scans; but I appreciate Linus's frustration that it could be much better.
Hugh
[PATCH 4/3] mm,thp,rmap: handle the normal !PageCompound case first
In reply to Hugh DickinsCommit ("mm,thp,rmap: lock_compound_mapcounts() on THP mapcounts") propagated the "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern throughout; but Linus hated the way that gives primacy to the uncommon case: switch to "if (!PageCompound) {atomic} else if (compound) {lock} else {lock}" throughout. Linus has a bigger idea for how to improve it all, but here just make that rearrangement.
--- mm/rmap.c | 54 +++++++++++++++++++++++++++--------------------------- 1 file changed, 27 insertions(+), 27 deletions(-)
mm/rmap.c +27 -27
@@ -1311,7 +1311,11 @@ void page_add_anon_rmap(struct page *page,else VM_BUG_ON_PAGE (!PageLocked (page), page); -if (compound &&PageTransHuge (page)) { +if (likely (!PageCompound (page))) { + first =atomic_inc_and_test (&page->_mapcount); + nr = first; + + }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); first = !mapcounts.compound_mapcount; mapcounts.compound_mapcount++;
@@ -1321,8 +1325,7 @@ void page_add_anon_rmap(struct page *page, nr =nr_subpages_unmapped (page, nr_pmdmapped); }unlock_compound_mapcounts (page, &mapcounts); - - }else if (PageCompound (page)) { + }else {struct page *head =compound_head (page);lock_compound_mapcounts (head, &mapcounts);
@@ -1330,10 +1333,6 @@ void page_add_anon_rmap(struct page *page, first =subpage_mapcount_inc (page); nr = first && !mapcounts.compound_mapcount;unlock_compound_mapcounts (head, &mapcounts); - - }else { - first =atomic_inc_and_test (&page->_mapcount); - nr = first; }VM_BUG_ON_PAGE (!first && (flags &RMAP_EXCLUSIVE ), page);
@@ -1373,20 +1372,23 @@ void page_add_anon_rmap(struct page *page,void page_add_new_anon_rmap (struct page *page,struct vm_area_struct *vma,unsigned long address) { -const bool compound =PageCompound (page); -int nr = compound ?thp_nr_pages (page) :1 ; +int nr;VM_BUG_ON_VMA (address < vma->vm_start || address >= vma->vm_end, vma);__SetPageSwapBacked (page); -if (compound) { + +if (likely (!PageCompound (page))) { +/* increment count (starts at -1) */ +atomic_set (&page->_mapcount,0 ); + nr =1 ; + }else {VM_BUG_ON_PAGE (!PageTransHuge (page), page);/* increment count (starts at -1) */ atomic_set (compound_mapcount_ptr (page),0 ); + nr =thp_nr_pages (page);__mod_lruvec_page_state (page,NR_ANON_THPS , nr); - }else { -/* increment count (starts at -1) */ -atomic_set (&page->_mapcount,0 ); } +__mod_lruvec_page_state (page,NR_ANON_MAPPED , nr);__page_set_anon_rmap (page, vma, address,1 ); }
@@ -1409,7 +1411,11 @@ void page_add_file_rmap(struct page *page,VM_BUG_ON_PAGE (compound && !PageTransHuge (page), page);lock_page_memcg (page); -if (compound &&PageTransHuge (page)) { +if (likely (!PageCompound (page))) { + first =atomic_inc_and_test (&page->_mapcount); + nr = first; + + }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); first = !mapcounts.compound_mapcount; mapcounts.compound_mapcount++;
@@ -1419,8 +1425,7 @@ void page_add_file_rmap(struct page *page, nr =nr_subpages_unmapped (page, nr_pmdmapped); }unlock_compound_mapcounts (page, &mapcounts); - - }else if (PageCompound (page)) { + }else {struct page *head =compound_head (page);lock_compound_mapcounts (head, &mapcounts);
@@ -1428,10 +1433,6 @@ void page_add_file_rmap(struct page *page, first =subpage_mapcount_inc (page); nr = first && !mapcounts.compound_mapcount;unlock_compound_mapcounts (head, &mapcounts); - - }else { - first =atomic_inc_and_test (&page->_mapcount); - nr = first; }if (nr_pmdmapped)
@@ -1471,7 +1472,11 @@ void page_remove_rmap(struct page *page,lock_page_memcg (page);/* page still mapped by someone else? */ -if (compound &&PageTransHuge (page)) { +if (likely (!PageCompound (page))) { + last =atomic_add_negative (-1 , &page->_mapcount); + nr = last; + + }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); mapcounts.compound_mapcount--; last = !mapcounts.compound_mapcount;
@@ -1481,8 +1486,7 @@ void page_remove_rmap(struct page *page, nr =nr_subpages_unmapped (page, nr_pmdmapped); }unlock_compound_mapcounts (page, &mapcounts); - - }else if (PageCompound (page)) { + }else {struct page *head =compound_head (page);lock_compound_mapcounts (head, &mapcounts);
@@ -1490,10 +1494,6 @@ void page_remove_rmap(struct page *page, last =subpage_mapcount_dec (page); nr = last && !mapcounts.compound_mapcount;unlock_compound_mapcounts (head, &mapcounts); - - }else { - last =atomic_add_negative (-1 , &page->_mapcount); - nr = last; }if (nr_pmdmapped) {
Signature · 1 line
2.35.3
Re: [PATCH 4/3] mm,thp,rmap: handle the normal !PageCompound case first
Quoted 6 lines · Hugh Dickins
Commit ("mm,thp,rmap:
lock_compound_mapcounts()on THP mapcounts") propagated the "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern throughout; but Linus hated the way that gives primacy to the uncommon case: switch to "if (!PageCompound) {atomic} else if (compound) {lock} else {lock}" throughout.
Side note, that 'compound' naming is also on my list of "I'm _really_ not a fan".
We actually have a completely different meaning for PageCompound() than the meaning of 'compound' in the rmap functions, and those functions literally mix those meanings if not on the same line, then at least right next to each other.
What 'rmap' actually means with 'compound' in the add/remove functions is basically 'not PAGE_SIZE' as far as I can tell.
So if I get the energy to do the rmap counts, I will *also* be renaming that horrible thing completely.
In fact, I'd be inclined to just pass in the actual page size (possibly a page shift order), which some of the functions want anyway, and which would be a lot clearer than the horrid "compound" name.
One reason I find the "compound" name so horrifying is that it is used very much for HUGETLB pages, which I don't think end up ever being marked as PageCompund(), and which are - for various historical reasons - doubly confusing because they use a "pte_t" to describe themselves, even when they are actually using a "pmd_t" or a "pud_t" to actually map the page.
So a HUGETLB entry really is (for historical reasons) designed to look like a single last-level pte_t entry, but from an rmap perspective it is explicitly *not* made to look like that at all, completely violating the HUGETLB design.
So the rmap code has several really REALLY confusing cases:
- the common one: just a page mapped at a *real* pte_t level.
To make that more confusing, it can actually be a single-page
_part_ of a compound page in the PageCompound() sense, but the rmap 'compound' argument will *not* be set, because from a *mmap* standpoint it's mapped as a single page.
This is generally recognized by the rmap code by 'compound' being zero.
- a HUGETLB mapping, which uses '->pte' in the page walking (please
kill me now) and is *not* using a PageCompund() page, but 'compound' is still set, because from a *mapping* standpoint it's not a final pte_t entry (buit from a MM design standpoint it _was_ supposed to be designed like a single page).
This is randomly recognized by looking at the vma flags (using
"is_vm_hugetlb_page(vma)") or just inherent in the code itself (ie the 'hugetlb()' functions are only called by code that has tested this situation one way or another)
To make things more confusing, some places use PageHeadHuge()
instead (but the folio version of said test is called "folio_test_hugetlb()", just so that nobody could possibly ever accuse the HUGETLB code to have consistency).
You'd think that PageHeadHuge() is one of the functions that
checks the page flag bits. You'd be wrong. It's very very special.
- an *actual* PageCompound() page, mapped as such as a THP page (ie
mapped by a pmd, not a pte).
This may be the same page size as a HUGETLB mapping (and often is),
but it's a completely different case in every single way.
But like the HUGETLB case, the 'compound' argument will be set, and
now it's actually a compound page (but hey, so could the single page mapping case be too).
Unlike the HUGETLB case, the page walker does not use ->pte for
this, and some of the walkers will very much use that, ie folio_referenced_one() will do
if (pvmw.pte) { to distinguish the "natively mapped PageCompound()" case (no pte)
from the "map a single page" or from the HUGETLB case (yes pte).
There may be more cases than those three, and I may have confused myself and gotten some of the details wrong, but I did want to write the above diatribe out to
(a) see if somebody corrects me for any of the cases I enumerated
(b) see if somebody can point to yet another odd case
(c) see if somebody has suggestions for better and more obvious names
for that 'compound' argument in the rmap code
I do wish the HUGETLB case didn't use 'pte' for its notion of how HUGETLB entries are mapped, but that's literally how HUGETLB is
designed: it started life as a larger last-level pte.
It just means that it ends up being very confusing when from a page table walk perspective, you're walking a pud or a pmd entry, and then you see a 'pte_t' instead.
An example of that confusion is visible in try_to_unmap_one(), which can be called with a HUGEPTE page (well, folio), and that does
while (page_vma_mapped_walk(&pvmw)) {to find the rmap entries, but it can't do that
if (pvmw.pte) {test to see what mapping it's walking (since both regular pages and HUGETLB pages use that), so then it just keeps testing what kind of page that was passed in.
Which really smells very odd to me, but apparently it works, presumably because unlike THP there can be no splitting. But it's a case where the whole "was it a regular page or a HUGETLB page" is really really confusing/
And mm/hugetlb.c (and places like mm/pagewalk.c too) has a fair number of random casts as a result of this "it's not really a pte_t, but it's designed to look like one" thing.
This all really is understandable from a historical context, and from HUGETLB really being just kind of designed to be a bigger page (not a collection of small pages that can be mapped as a bigger entity), but it really does mean that 'rmap' calling those HUGETLB pages 'compound' is conceptually very very wrong.
Oh well. That whole HUGETLB model isn't getting fixed, but I think the naming confusion about 'compound' *can* be fixed fairly easily, and we could try to at least avoid having 'compound' and 'PageCompound()' mean totally different things in the same function.
I'm not going to do any of this cleanup now, but I wanted to at least voice my concerns. Maybe I'll get around to actually trying to clarify the code later.
Because this was all stuff that was *very* confusing when I did the rmap simplification in that (now completely rewritten to explicitly _not_ touch rmap at all) original version of the delayed rmap patch series.
Linus
Re: [PATCH 4/3] mm,thp,rmap: handle the normal !PageCompound case first
Quoted 16 lines · Linus Torvalds
Quoted 6 lines · Hugh Dickins
Commit ("mm,thp,rmap:
lock_compound_mapcounts()on THP mapcounts") propagated the "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern throughout; but Linus hated the way that gives primacy to the uncommon case: switch to "if (!PageCompound) {atomic} else if (compound) {lock} else {lock}" throughout.Side note, that 'compound' naming is also on my list of "I'm _really_ not a fan".
We actually have a completely different meaning for
PageCompound()than the meaning of 'compound' in the rmap functions, and those functions literally mix those meanings if not on the same line, then at least right next to each other.
Quoted 4 lines
What 'rmap' actually means with 'compound' in the add/remove functions is basically 'not
PAGE_SIZE' as far as I can tell.So if I get the energy to do the rmap counts,
See other mail, I got some zest to try your idea on the counts.
Quoted 1 line
I will *also* be renaming that horrible thing completely.
But I don't suppose I'll spend time on that part, I don't really see the problem. "compound" might be better named, say, "large_rmap" (I'd have said "pmd_mapped" or "pmd_rmap", but you raise the spectre of hugetlb below, and powerpc as usual does hugetlb very differently), but compound seems okay to me, and consistent with usage elsewhere.
Quoted 5 lines
In fact, I'd be inclined to just pass in the actual page size (possibly a page shift order), which some of the functions want anyway, and which would be a lot clearer than the horrid "compound" name.
But yes, I think that would be an improvement; yet you might find a reason why so often we don't do that - there's often an awkward BUILD_BUG when you build without CONFIG_TRANSPARENT_HUGEPAGE=y. And much as I've often wanted to remove it, it does give some assurance that we're not bloating THP-disabled configs. Maybe the steady growth of compound_nr() usage gets around that better now (or will you be renaming that too ?-)
Quoted 4 lines
One reason I find the "compound" name so horrifying is that it is used very much for HUGETLB pages, which I don't think end up ever being marked as
PageCompund(), and which are - for various historical
hugetlb pages are always PageCompound. Shoot me if they're not.
Quoted 3 lines
reasons - doubly confusing because they use a "
pte_t" to describe themselves, even when they are actually using a "pmd_t" or a "pud_t" to actually map the page.
Yes, I wish we would undo that hugetlb deception: it would probably be much more (un)doable, were it not for powerpc (and ia64 iirc).
Quoted 6 lines
So a HUGETLB entry really is (for historical reasons) designed to look like a single last-level
pte_tentry, but from an rmap perspective it is explicitly *not* made to look like that at all, completely violating the HUGETLB design.
Quoted 8 lines
So the rmap code has several really REALLY confusing cases:
- the common one: just a page mapped at a *real*
pte_tlevel.To make that more confusing, it can actually be a single-page
_part_ of a compound page in thePageCompound()sense, but the rmap 'compound' argument will *not* be set, because from a *mmap* standpoint it's mapped as a single page.
Yes. Most pages are unambiguous, but when a PageHead page arrives at page_add/remove_rmap(), we have to do different things, according to whether it's mapped with a large or a small entry.
But I'm going away at this point, you write much faster than I can read and understand and respond. I'm responding in part to "fix" my stupid typo on Johannes's address.
Hugh
Quoted 103 lines
This is generally recognized by the rmap code by 'compound' being zero.
- a HUGETLB mapping, which uses '->pte' in the page walking (please
kill me now) and is *not* using aPageCompund()page, but 'compound' is still set, because from a *mapping* standpoint it's not a finalpte_tentry (buit from a MM design standpoint it _was_ supposed to be designed like a single page).This is randomly recognized by looking at the vma flags (using
"is_vm_hugetlb_page(vma)") or just inherent in the code itself (ie the 'hugetlb()' functions are only called by code that has tested this situation one way or another)To make things more confusing, some places use
PageHeadHuge()
instead (but the folio version of said test is called "folio_test_hugetlb()", just so that nobody could possibly ever accuse the HUGETLB code to have consistency).You'd think that
PageHeadHuge()is one of the functions that
checks the page flag bits. You'd be wrong. It's very very special.- an *actual*
PageCompound()page, mapped as such as a THP page (ie
mapped by a pmd, not a pte).This may be the same page size as a HUGETLB mapping (and often is),
but it's a completely different case in every single way.But like the HUGETLB case, the 'compound' argument will be set, and
now it's actually a compound page (but hey, so could the single page mapping case be too).Unlike the HUGETLB case, the page walker does not use ->pte for
this, and some of the walkers will very much use that, iefolio_referenced_one()will doif (pvmw.pte) {to distinguish the "natively mapped
PageCompound()" case (no pte)
from the "map a single page" or from the HUGETLB case (yes pte).There may be more cases than those three, and I may have confused myself and gotten some of the details wrong, but I did want to write the above diatribe out to
(a) see if somebody corrects me for any of the cases I enumerated
(b) see if somebody can point to yet another odd case
(c) see if somebody has suggestions for better and more obvious names
for that 'compound' argument in the rmap codeI do wish the HUGETLB case didn't use 'pte' for its notion of how HUGETLB entries are mapped, but that's literally how HUGETLB is
designed: it started life as a larger last-level pte.It just means that it ends up being very confusing when from a page table walk perspective, you're walking a pud or a pmd entry, and then you see a '
pte_t' instead.An example of that confusion is visible in
try_to_unmap_one(), which can be called with a HUGEPTE page (well, folio), and that doeswhile (page_vma_mapped_walk(&pvmw)) {to find the rmap entries, but it can't do that
if (pvmw.pte) {test to see what mapping it's walking (since both regular pages and HUGETLB pages use that), so then it just keeps testing what kind of page that was passed in.
Which really smells very odd to me, but apparently it works, presumably because unlike THP there can be no splitting. But it's a case where the whole "was it a regular page or a HUGETLB page" is really really confusing/
And
mm/hugetlb.c(and places likemm/pagewalk.ctoo) has a fair number of random casts as a result of this "it's not really apte_t, but it's designed to look like one" thing.This all really is understandable from a historical context, and from HUGETLB really being just kind of designed to be a bigger page (not a collection of small pages that can be mapped as a bigger entity), but it really does mean that 'rmap' calling those HUGETLB pages 'compound' is conceptually very very wrong.
Oh well. That whole HUGETLB model isn't getting fixed, but I think the naming confusion about 'compound' *can* be fixed fairly easily, and we could try to at least avoid having 'compound' and '
PageCompound()' mean totally different things in the same function.I'm not going to do any of this cleanup now, but I wanted to at least voice my concerns. Maybe I'll get around to actually trying to clarify the code later.
Because this was all stuff that was *very* confusing when I did the rmap simplification in that (now completely rewritten to explicitly _not_ touch rmap at all) original version of the delayed rmap patch series.
Linus
Re: [PATCH 4/3] mm,thp,rmap: handle the normal !PageCompound case first
In reply to Linus TorvaldsQuoted 11 lines · Linus Torvalds
Quoted 6 lines · Hugh Dickins
Commit ("mm,thp,rmap:
lock_compound_mapcounts()on THP mapcounts") propagated the "if (compound) {lock} else if (PageCompound) {lock} else {atomic}" pattern throughout; but Linus hated the way that gives primacy to the uncommon case: switch to "if (!PageCompound) {atomic} else if (compound) {lock} else {lock}" throughout.Side note, that 'compound' naming is also on my list of "I'm _really_ not a fan".
Quoted 7 lines
We actually have a completely different meaning for
PageCompound()than the meaning of 'compound' in the rmap functions, and those functions literally mix those meanings if not on the same line, then at least right next to each other.What 'rmap' actually means with 'compound' in the add/remove functions is basically 'not
PAGE_SIZE' as far as I can tell.
Ah. I've been trying to understand what that 'compound' really means, and what the difference is to 'PageCompound()' and why we need both. Thanks!
Quoted 6 lines
One reason I find the "compound" name so horrifying is that it is used very much for HUGETLB pages, which I don't think end up ever being marked as
PageCompund(), and which are - for various historical reasons - doubly confusing because they use a "pte_t" to describe themselves, even when they are actually using a "pmd_t" or a "pud_t" to actually map the page.
HugeTLB pages _are_ marked as Compound. There's some fairly horrific code to manually make them compound when they have to be allocated piecemeal (because they're 1GB and too large for the page allocator).
Quoted 4 lines
To make things more confusing, some places use
PageHeadHuge()
instead (but the folio version of said test is called "folio_test_hugetlb()", just so that nobody could possibly ever accuse the HUGETLB code to have consistency).
That one's my fault, but it's a reaction to all the times that I and others have got confused between PageHuge and PageTransHuge. I suppose we could do a big sed s/PageHuge/PageHugeTLB/, but I'm hopeful the entire hugetlb codebase is either converted to folios or unified with THP handling.
Quoted 7 lines
I do wish the HUGETLB case didn't use 'pte' for its notion of how HUGETLB entries are mapped, but that's literally how HUGETLB is
designed: it started life as a larger last-level pte.It just means that it ends up being very confusing when from a page table walk perspective, you're walking a pud or a pmd entry, and then you see a '
pte_t' instead.
Yes, one of the long-term things I want to try is making the hugetlb code use the pmd/pud types like the THP code does.
Re: [PATCH 4/3] mm,thp,rmap: handle the normal !PageCompound case first
Quoted 3 lines · Matthew Wilcox
Ah. I've been trying to understand what that 'compound' really means, and what the difference is to '
PageCompound()' and why we need both.
Yeah, so the 'why' is:
(a) to distinguish the case of "I'm mapping the first sub-page of a
compound page as a _single_ page page entry in the pte" from "I'm mapping the whole compound/THP/HUGETLB page as a pmd"
The actual 'page' pointer can be the same in both cases, so you can't tell from that: PageCompound() will be true in both cases.
Of course, sometimes you *can* tell from the page pointer too (eg the HUGETLB case can never be mapped as a small page), but not always.
(b) because we do completely different things from a page locking and
statistics standpoint for the two cases.
That (b) is obviously related to (a), but it's effectively the main reason why rmap needs to be able to tell the difference in the first place.
Quoted 1 line
HugeTLB pages _are_ marked as Compound.
Oh, ok. It's not clear why they would be, and historically I don't think they were, but I guess it's for random implementation details (probably to look up the head page logic).
Quoted 3 lines
There's some fairly horrific
code to manually make them compound when they have to be allocated piecemeal (because they're 1GB and too large for the page allocator).
Yeah, the HUGETLB case is a mess these days, but it made sense historically, because it was a much simpler thing than the THP pages that have all the fragmentation cases.
Now that we handle pmd-sized pages anyway, the HUGETLB case is mostly just a nasty oddity, but we obviously also do the pud case with HUGETLB.
And who knows what ia64 did with its completely random page-size thing. I don't even want to think about it, and thankfully these days I don't feel like I need to care any more ;)
Quoted 10 lines
Quoted 4 lines
To make things more confusing, some places use
PageHeadHuge()
instead (but the folio version of said test is called "folio_test_hugetlb()", just so that nobody could possibly ever accuse the HUGETLB code to have consistency).That one's my fault, but it's a reaction to all the times that I and others have got confused between PageHuge and PageTransHuge. I suppose we could do a big sed s/PageHuge/PageHugeTLB/, but I'm hopeful the entire hugetlb codebase is either converted to folios or unified with THP handling.
Yeah, it would be lovely to make HUGETLB some THP special case some day.
Linus
cover mm,thp,rmap: rework the use of subpages_mapcount
In reply to Hugh DickinsLinus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - except rmap.c still using lock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.
1/3 mm,thp,rmap: subpages_mapcount of PTE-mapped subpages 2/3 mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped 3/3 mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
Documentation/mm/transhuge.rst | 10 +- include/linux/mm.h | 65 +++++++---- include/linux/rmap.h | 12 +- mm/debug.c | 2 +- mm/huge_memory.c | 15 +-- mm/rmap.c | 213 ++++++++++------------------------- 6 files changed, 119 insertions(+), 198 deletions(-)
Hugh
PATCH 1/3 mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
Following suggestion from Linus, instead of counting every PTE map of a compound page in subpages_mapcount, just count how many of its subpages are PTE-mapped: this yields the exact number needed for NR_ANON_MAPPED and NR_FILE_MAPPED stats, without any need for a locked scan of subpages; and requires updating the count less often.
This does then revert total_mapcount() and folio_mapcount() to needing a scan of subpages; but they are inherently racy, and need no locking, so Linus is right that the scans are much better done there. Plus (unlike in 6.1 and previous) subpages_mapcount lets us avoid the scan in the common case of no PTE maps. And page_mapped() and folio_mapped() remain scanless and just as efficient with the new meaning of subpages_mapcount:
those are the functions which I most wanted to remove the scan from.
The updated page_dup_compound_rmap() is no longer suitable for use by anon THP's __split_huge_pmd_locked(); but page_add_anon_rmap() can be used for that, so long as its VM_BUG_ON_PAGE(!PageLocked) is deleted.
Evidence is that this way goes slightly faster than the previous implementation for most cases; but significantly faster in the (now scanless) pmds after ptes case, which started out at 870ms and was brought down to 495ms by the previous series, now takes around 105ms.
--- Documentation/mm/transhuge.rst | 3 +- include/linux/mm.h | 52 ++++++----- include/linux/rmap.h | 8 +- mm/huge_memory.c | 2 +- mm/rmap.c | 155 ++++++++++++++------------------- 5 files changed, 103 insertions(+), 117 deletions(-)
Documentation/mm/transhuge.rst +2 -1
@@ -122,7 +122,8 @@ pages: - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement - ->subpages_mapcount, stored in first tail page of the compound page. + ->subpages_mapcount, stored in first tail page of the compound page, when + _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. In order to have race-free accounting of sub-pages mapped, changes to sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are are all locked by bit_spin_lock of PG_locked in the first tail ->flags.
include/linux/mm.h +31 -21
76 lines not on this page · raw message
include/linux/rmap.h +4 -4
@@ -204,14 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -void page_dup_compound_rmap (struct page *page,bool compound); +void page_dup_compound_rmap (struct page *page);static inline void page_dup_file_rmap (struct page *page,bool compound) { -if (PageCompound (page)) -page_dup_compound_rmap (page, compound); -else +if (likely (!compound/* page is mapped by PTE */ ))atomic_inc (&page->_mapcount); +else +page_dup_compound_rmap (page); }/**
mm/huge_memory.c +1 -1
@@ -2215,7 +2215,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry);if (!pmd_migration) -page_dup_compound_rmap (page + i, false); +page_add_anon_rmap (page + i, vma, addr, false);pte_unmap (pte); }
mm/rmap.c +65 -90
227 lines not on this page · raw message
Signature · 1 line
2.35.3
Re: [PATCH 1/3] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
On Fri, Nov 18, 2022 at 2:12 AM Hugh Dickins <[email protected]> wrote:
...
Quoted 35 lines
mm/rmap.c +13
-8@@ -1308,31 +1285,29 @@ void page_add_anon_rmap(struct page *page,if (unlikely (PageKsm (page)))lock_page_memcg (page); -else -VM_BUG_ON_PAGE (!PageLocked (page), page); -if (likely (!PageCompound (page))) { +if (likely (!compound/* page is mapped by PTE */ )) { first =atomic_inc_and_test (&page->_mapcount); nr = first; +if (first &&PageCompound (page)) { +struct page *head =compound_head (page); + +lock_compound_mapcounts (head, &mapcounts); + mapcounts.subpages_mapcount++; + nr = !mapcounts.compound_mapcount; +unlock_compound_mapcounts (head, &mapcounts); + } + }else if (PageTransHuge (page)) { +/* That test is redundant: it's for safety or to optimize out */ - }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); first = !mapcounts.compound_mapcount; mapcounts.compound_mapcount++;if (first) { - nr = nr_pmdmapped =thp_nr_pages (page); -if (mapcounts.subpages_mapcount) - nr =nr_subpages_unmapped (page, nr_pmdmapped); + nr_pmdmapped =thp_nr_pages (page); + nr = nr_pmdmapped - mapcounts.subpages_mapcount; }unlock_compound_mapcounts (page, &mapcounts); - }else {
mm/rmap.c void page_add_anon_rmap(struct page *page, · line 1313
Quoted 10 lines
mm/rmap.c +0
-7-struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount++; - first =subpage_mapcount_inc (page); - nr = first && !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); }VM_BUG_ON_PAGE (!first && (flags &RMAP_EXCLUSIVE ), page);
Hi Hugh, I got the following warning from the removed "else" branch. Is it legit? Thanks.
mm/rmap.c:1236:13: warning: variable 'first' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
} else if (PageTransHuge(page)) {
^~~~~~~~~~~~~~~~~~~
mm/rmap.c:1248:18: note: uninitialized use occurs here
VM_BUG_ON_PAGE(!first && (flags & RMAP_EXCLUSIVE), page);
^~~~~Re: [PATCH 1/3] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
Quoted 5 lines · Yu Zhao
On Fri, Nov 18, 2022 at 2:12 AM Hugh Dickins <[email protected]> wrote:
...
Quoted 1 line
(quoted diff) +0
-0@@ -1308,31 +1285,29 @@ void page_add_anon_rmap(struct page *page,
...
Quoted 6 lines
Quoted 2 lines
VM_BUG_ON_PAGE(!first && (flags & RMAP_EXCLUSIVE), page);Hi Hugh, I got the following warning from the removed "else" branch. Is it legit? Thanks.
Quoted 7 lines
mm/rmap.c:1236:13: warning: variable 'first' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]} else if (PageTransHuge(page)) { ^~~~~~~~~~~~~~~~~~~ mm/rmap.c:1248:18: note: uninitialized use occurs here VM_BUG_ON_PAGE(!first && (flags & RMAP_EXCLUSIVE), page); ^~~~~
Thanks a lot for that. From the compiler's point of view, it is certainly a legit warning. From our point of view, it's unimportant, because we know that page_add_anon_rmap() should only ever be called with compound true when PageTransHuge(page) (and should never be called with compound true when TRANSPARENT_HUGEPAGE is disabled):
so it's a "system error" if first is uninitialized there.
But none of us want a compiler warning: I'll follow up with a fix patch, when I've decided whether it's better initialized to true or to false in the impossible case...
Although the same pattern is used in other functions, this is the only one of them which goes on to use "first" or "last" afterwards.
Hugh
PATCH 1/3 mm,thp,rmap: subpages_mapcount of PTE-mapped subpages: fix
Yu Zhao reports compiler warning in page_add_anon_rmap():
mm/rmap.c:1236:13: warning: variable 'first' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
} else if (PageTransHuge(page)) {
^~~~~~~~~~~~~~~~~~~
mm/rmap.c:1248:18: note: uninitialized use occurs here
VM_BUG_ON_PAGE(!first && (flags & RMAP_EXCLUSIVE), page);
^~~~~We do need to fix that, even though it's only uninitialized in an impossible condition: I've chosen to initialize "first" true, to minimize the BUGs it might then hit; but you could just as well choose to initialize it false, to maximize the BUGs it might hit.
--- mm/rmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/rmap.c +1 -1
@@ -1281,7 +1281,7 @@ void page_add_anon_rmap(struct page *page,struct compound_mapcounts mapcounts;int nr =0 , nr_pmdmapped =0 ;bool compound = flags &RMAP_COMPOUND ; -bool first; +bool first = true;if (unlikely (PageKsm (page)))lock_page_memcg (page);
Signature · 1 line
2.35.3
Re: [PATCH 1/3 fix] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages: fix
Quoted 26 lines · Hugh Dickins
Yu Zhao reports compiler warning in
page_add_anon_rmap():
mm/rmap.c:1236:13: warning: variable 'first' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]} else if (PageTransHuge(page)) { ^~~~~~~~~~~~~~~~~~~ mm/rmap.c:1248:18: note: uninitialized use occurs here VM_BUG_ON_PAGE(!first && (flags & RMAP_EXCLUSIVE), page); ^~~~~We do need to fix that, even though it's only uninitialized in an impossible condition: I've chosen to initialize "first" true, to minimize the BUGs it might then hit; but you could just as well choose to initialize it false, to maximize the BUGs it might hit.
Reported-by Yu Zhao <[email protected]>Signed-off-by Hugh Dickins <[email protected]>--- mm/rmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)mm/rmap.c +0
-0
mm/rmap.c void page_add_anon_rmap(struct page *page, · line 1287
Quoted 8 lines
mm/rmap.c +1
-1@@ -1281,7 +1281,7 @@ void page_add_anon_rmap(struct page *page,struct compound_mapcounts mapcounts;int nr =0 , nr_pmdmapped =0 ;bool compound = flags &RMAP_COMPOUND ; -bool first; +bool first = true;if (unlikely (PageKsm (page)))lock_page_memcg (page);
Other option is to drop PageTransHuge() check that you already claim to be redundant.
Or have else BUG() to catch cases where the helper called with compound=true on non-THP page.
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 1/3 fix] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages: fix
Quoted 1 line · Kirill A. Shutemov
On Fri, Nov 18, 2022 at 05:35:05PM -0800, Hugh Dickins wrote:
...
Quoted 9 lines
Quoted 9 lines
mm/rmap.c +1
-1@@ -1281,7 +1281,7 @@ void page_add_anon_rmap(struct page *page,struct compound_mapcounts mapcounts;int nr =0 , nr_pmdmapped =0 ;bool compound = flags &RMAP_COMPOUND ; -bool first; +bool first = true;
Quoted 8 lines
mm/rmap.c void page_add_anon_rmap(struct page *page, · line 1287
Quoted 2 lines
mm/rmap.c +0
-0if (unlikely (PageKsm (page)))lock_page_memcg (page);Other option is to drop
PageTransHuge()check that you already claim to be redundant.Or have else
BUG()to catch cases where the helper called with compound=true on non-THP page.
I'm sticking with the "first = true". I did receive a report of bloating some tiny config a little, on the very first series, so I've been on guard since then about adding THP code where the optimizer cannot see to remove
it: so do want to keep the PageTransHuge check in there. Could be done in other ways, yes, but I'd ended up feeling this was the best compromise.
Hugh
Re: [PATCH 1/3] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
In reply to Hugh DickinsQuoted 18 lines · Hugh Dickins
Following suggestion from Linus, instead of counting every PTE map of a compound page in
subpages_mapcount, just count how many of its subpages are PTE-mapped: this yields the exact number needed forNR_ANON_MAPPEDandNR_FILE_MAPPEDstats, without any need for a locked scan of subpages; and requires updating the count less often.This does then revert
total_mapcount()andfolio_mapcount()to needing a scan of subpages; but they are inherently racy, and need no locking, so Linus is right that the scans are much better done there. Plus (unlike in 6.1 and previous)subpages_mapcountlets us avoid the scan in the common case of no PTE maps. Andpage_mapped()andfolio_mapped()remain scanless and just as efficient with the new meaning ofsubpages_mapcount:
those are the functions which I most wanted to remove the scan from.The updated
page_dup_compound_rmap()is no longer suitable for use by anon THP's__split_huge_pmd_locked(); butpage_add_anon_rmap()can be used for that, so long as itsVM_BUG_ON_PAGE(!PageLocked)is deleted.
Quoted 7 lines
Evidence is that this way goes slightly faster than the previous implementation for most cases; but significantly faster in the (now scanless) pmds after ptes case, which started out at 870ms and was brought down to 495ms by the previous series, now takes around 105ms.
Suggested-by Linus Torvalds <[email protected]>Signed-off-by Hugh Dickins <[email protected]>
Few minor nitpicks below.
Quoted 113 lines
--- Documentation/mm/transhuge.rst | 3 +- include/linux/mm.h | 52 ++++++----- include/linux/rmap.h | 8 +- mm/huge_memory.c | 2 +- mm/rmap.c | 155 ++++++++++++++------------------- 5 files changed, 103 insertions(+), 117 deletions(-)Documentation/mm/transhuge.rst +2
-1@@ -122,7 +122,8 @@ pages: - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement - ->subpages_mapcount, stored in first tail page of the compound page. + ->subpages_mapcount, stored in first tail page of the compound page, when + _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. In order to have race-free accounting of sub-pages mapped, changes to sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are are all locked by bit_spin_lock of PG_locked in the first tail ->flags.include/linux/mm.h +31
-21@@ -828,7 +828,7 @@ static inline int head_compound_mapcount(struct page *head) }/* -* Sum of mapcounts of sub-pages, does not include compound mapcount. +* Number of sub-pages mapped by PTE, does not include compound mapcount. * Must be called only on head of compound page. */ static inline int head_subpages_mapcount (struct page *head)@@ -864,23 +864,7 @@ static inline int page_mapcount(struct page *page)return head_compound_mapcount (page) + mapcount; } -static inline int total_mapcount (struct page *page) -{ -if (likely (!PageCompound (page))) -return atomic_read (&page->_mapcount) +1 ; - page =compound_head (page); -return head_compound_mapcount (page) +head_subpages_mapcount (page); -} - -/* -* Return true if this page is mapped into pagetables. -* For compound page it returns true if any subpage of compound page is mapped, -* even if this particular subpage is not itself mapped by any PTE or PMD. -*/ -static inline bool page_mapped (struct page *page) -{ -return total_mapcount (page) >0 ; -} +int total_compound_mapcount (struct page *head);/** * folio_mapcount() - Calculate the number of mappings of this folio. @@ -897,8 +881,20 @@ static inline int folio_mapcount(struct folio *folio) {if (likely (!folio_test_large (folio)))return atomic_read (&folio->_mapcount) +1 ; -return atomic_read (folio_mapcount_ptr (folio)) +1 + -atomic_read (folio_subpages_mapcount_ptr (folio)); +return total_compound_mapcount (&folio->page); +} + +static inline int total_mapcount (struct page *page) +{ +if (likely (!PageCompound (page))) +return atomic_read (&page->_mapcount) +1 ; +return total_compound_mapcount (compound_head (page)); +} + +static inline bool folio_large_is_mapped (struct folio *folio) +{ +return atomic_read (folio_mapcount_ptr (folio)) + +atomic_read (folio_subpages_mapcount_ptr (folio)) >=0 ; }/** @@ -909,7 +905,21 @@ static inline int folio_mapcount(struct folio *folio)*/ static inline bool folio_mapped (struct folio *folio) { -return folio_mapcount (folio) >0 ; +if (likely (!folio_test_large (folio))) +return atomic_read (&folio->_mapcount) >=0 ; +return folio_large_is_mapped (folio); +} + +/* +* Return true if this page is mapped into pagetables. +* For compound page it returns true if any sub-page of compound page is mapped, +* even if this particular sub-page is not itself mapped by any PTE or PMD. +*/ +static inline bool page_mapped (struct page *page) +{ +if (likely (!PageCompound (page))) +return atomic_read (&page->_mapcount) >=0 ; +return folio_large_is_mapped (page_folio (page)); }static inline struct page *virt_to_head_page (const void *x)include/linux/rmap.h +0
-0@@ -204,14 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address);
include/linux/rmap.h void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *, · line 211
Quoted 10 lines
include/linux/rmap.h +2
-4-void page_dup_compound_rmap (struct page *page,bool compound); +void page_dup_compound_rmap (struct page *page);static inline void page_dup_file_rmap (struct page *page,bool compound) { -if (PageCompound (page)) -page_dup_compound_rmap (page, compound); -else +if (likely (!compound/* page is mapped by PTE */ ))
I'm not a fan of this kind of comments.
Maybe move above the line (here and below)?
Quoted 99 lines
include/linux/rmap.h +2
-0atomic_inc (&page->_mapcount); + else +page_dup_compound_rmap (page ); }/** mm/huge_memory.c +1
-1@@ -2215,7 +2215,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry);if (!pmd_migration) -page_dup_compound_rmap (page + i, false); +page_add_anon_rmap (page + i, vma, addr, false);pte_unmap (pte); }mm/rmap.c +19
-38@@ -1117,55 +1117,36 @@ static void unlock_compound_mapcounts(struct page *head,bit_spin_unlock (PG_locked, &head[1 ].flags); } -/* -* When acting on a compound page under lock_compound_mapcounts(), avoid the -* unnecessary overhead of an actual atomic operation on its subpage mapcount. -* Return true if this is the first increment or the last decrement -* (remembering that page->_mapcount -1 represents logical mapcount 0). -*/ -static bool subpage_mapcount_inc (struct page *page) -{ -int orig_mapcount =atomic_read (&page->_mapcount); - -atomic_set (&page->_mapcount, orig_mapcount +1 ); -return orig_mapcount <0 ; -} - -static bool subpage_mapcount_dec (struct page *page) -{ -int orig_mapcount =atomic_read (&page->_mapcount); - -atomic_set (&page->_mapcount, orig_mapcount -1 ); -return orig_mapcount ==0 ; -} - -/* -* When mapping a THP's first pmd, or unmapping its last pmd, if that THP -* also has pte mappings, then those must be discounted: in order to maintain -* NR_ANON_MAPPED and NR_FILE_MAPPED statistics exactly, without any drift, -* and to decide when an anon THP should be put on the deferred split queue. -* This function must be called between lock_ and unlock_compound_mapcounts(). -*/ -static int nr_subpages_unmapped (struct page *head,int nr_subpages) +int total_compound_mapcount (struct page *head) { -int nr = nr_subpages; +int mapcount =head_compound_mapcount (head); +int nr_subpages;int i; -/* Discount those subpages mapped by pte */ +/* In the common case, avoid the loop when no subpages mapped by PTE */ +if (head_subpages_mapcount (head) ==0 ) +return mapcount; +/* +* Add all the PTE mappings of those subpages mapped by PTE. +* Limit the loop, knowing that only subpages_mapcount are mapped? +* Perhaps: given all the raciness, that may be a good or a bad idea. +*/ + nr_subpages =thp_nr_pages (head);for (i =0 ; i < nr_subpages; i++) -if (atomic_read (&head[i]._mapcount) >=0 ) - nr--; -return nr; + mapcount +=atomic_read (&head[i]._mapcount); + +/* But each of those _mapcounts was based on -1 */ + mapcount += nr_subpages; +return mapcount; }/* -* page_dup_compound_rmap(), used when copying mm, or when splitting pmd, +* page_dup_compound_rmap(), used when copying mm, * provides a simple example of using lock_ and unlock_compound_mapcounts(). */ -void page_dup_compound_rmap (struct page *page,bool compound) +void page_dup_compound_rmap (struct page *head) {struct compound_mapcounts mapcounts; -struct page *head;/* * Hugetlb pages could use lock_compound_mapcounts(), like THPs do;
mm/rmap.c void page_dup_compound_rmap(struct page *page, bool compound) · line 1162
Quoted 10 lines
mm/rmap.c +2
-4@@ -1176,20 +1157,16 @@ void page_dup_compound_rmap(struct page *page, bool compound)* Note that hugetlb does not call page_add_file_rmap(): * here is where hugetlb shared page mapcount is raised. */ -if (PageHuge (page)) { -atomic_inc (compound_mapcount_ptr (page)); -return ; - } +if (PageHuge (head)) { +atomic_inc (compound_mapcount_ptr (head));
Remove the newline?
Quoted 149 lines
mm/rmap.c +44
-48- head =compound_head (page); -lock_compound_mapcounts (head, &mapcounts); -if (compound) { + }else if (PageTransHuge (head)) { +/* That test is redundant: it's for safety or to optimize out */ + +lock_compound_mapcounts (head, &mapcounts); mapcounts.compound_mapcount++; - }else { - mapcounts.subpages_mapcount++; -subpage_mapcount_inc (page); +unlock_compound_mapcounts (head, &mapcounts); } -unlock_compound_mapcounts (head, &mapcounts); }/** @@ -1308,31 +1285,29 @@ void page_add_anon_rmap(struct page *page,if (unlikely (PageKsm (page)))lock_page_memcg (page); -else -VM_BUG_ON_PAGE (!PageLocked (page), page); -if (likely (!PageCompound (page))) { +if (likely (!compound/* page is mapped by PTE */ )) { first =atomic_inc_and_test (&page->_mapcount); nr = first; +if (first &&PageCompound (page)) { +struct page *head =compound_head (page); + +lock_compound_mapcounts (head, &mapcounts); + mapcounts.subpages_mapcount++; + nr = !mapcounts.compound_mapcount; +unlock_compound_mapcounts (head, &mapcounts); + } + }else if (PageTransHuge (page)) { +/* That test is redundant: it's for safety or to optimize out */ - }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); first = !mapcounts.compound_mapcount; mapcounts.compound_mapcount++;if (first) { - nr = nr_pmdmapped =thp_nr_pages (page); -if (mapcounts.subpages_mapcount) - nr =nr_subpages_unmapped (page, nr_pmdmapped); + nr_pmdmapped =thp_nr_pages (page); + nr = nr_pmdmapped - mapcounts.subpages_mapcount; }unlock_compound_mapcounts (page, &mapcounts); - }else { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount++; - first =subpage_mapcount_inc (page); - nr = first && !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); }VM_BUG_ON_PAGE (!first && (flags &RMAP_EXCLUSIVE ), page);@@ -1411,28 +1386,28 @@ void page_add_file_rmap(struct page *page,VM_BUG_ON_PAGE (compound && !PageTransHuge (page), page);lock_page_memcg (page); -if (likely (!PageCompound (page))) { +if (likely (!compound/* page is mapped by PTE */ )) { first =atomic_inc_and_test (&page->_mapcount); nr = first; +if (first &&PageCompound (page)) { +struct page *head =compound_head (page); + +lock_compound_mapcounts (head, &mapcounts); + mapcounts.subpages_mapcount++; + nr = !mapcounts.compound_mapcount; +unlock_compound_mapcounts (head, &mapcounts); + } + }else if (PageTransHuge (page)) { +/* That test is redundant: it's for safety or to optimize out */ - }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); first = !mapcounts.compound_mapcount; mapcounts.compound_mapcount++;if (first) { - nr = nr_pmdmapped =thp_nr_pages (page); -if (mapcounts.subpages_mapcount) - nr =nr_subpages_unmapped (page, nr_pmdmapped); + nr_pmdmapped =thp_nr_pages (page); + nr = nr_pmdmapped - mapcounts.subpages_mapcount; }unlock_compound_mapcounts (page, &mapcounts); - }else { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount++; - first =subpage_mapcount_inc (page); - nr = first && !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); }if (nr_pmdmapped)@@ -1472,28 +1447,28 @@ void page_remove_rmap(struct page *page,lock_page_memcg (page);/* page still mapped by someone else? */ -if (likely (!PageCompound (page))) { +if (likely (!compound/* page is mapped by PTE */ )) { last =atomic_add_negative (-1 , &page->_mapcount); nr = last; +if (last &&PageCompound (page)) { +struct page *head =compound_head (page); + +lock_compound_mapcounts (head, &mapcounts); + mapcounts.subpages_mapcount--; + nr = !mapcounts.compound_mapcount; +unlock_compound_mapcounts (head, &mapcounts); + } + }else if (PageTransHuge (page)) { +/* That test is redundant: it's for safety or to optimize out */ - }else if (compound &&PageTransHuge (page)) {lock_compound_mapcounts (page, &mapcounts); mapcounts.compound_mapcount--; last = !mapcounts.compound_mapcount;if (last) { - nr = nr_pmdmapped =thp_nr_pages (page); -if (mapcounts.subpages_mapcount) - nr =nr_subpages_unmapped (page, nr_pmdmapped); + nr_pmdmapped =thp_nr_pages (page); + nr = nr_pmdmapped - mapcounts.subpages_mapcount; }unlock_compound_mapcounts (page, &mapcounts); - }else { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount--; - last =subpage_mapcount_dec (page); - nr = last && !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); }if (nr_pmdmapped) {Signature · 1 line
2.35.3
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 1/3] mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
Quoted 3 lines · Kirill A. Shutemov
On Fri, Nov 18, 2022 at 01:12:03AM -0800, Hugh Dickins wrote:
Thanks a lot for all these, Kirill.
Quoted 3 lines
Few minor nitpicks below.
...
Quoted 10 lines
include/linux/rmap.h void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *, · line 211
Quoted 6 lines
static inline void
page_dup_file_rmap(struct page *page, bool compound){include/linux/rmap.h +1
-3-if (PageCompound (page)) -page_dup_compound_rmap (page, compound); -else +if (likely (!compound/* page is mapped by PTE */ ))I'm not a fan of this kind of comments.
Maybe move above the line (here and below)?
Okay, done throughout. I wouldn't have added those comments, but Linus had another "simmering hatred", of the "compound" arguments: he found them very confusing.
The real fix is to rename them, probably to pmd_mapped; or better, pass down an int nr_pages as he suggested; but I'm wary of the HPAGE_NR_PAGES build bug, and it wants to be propagated through various other files (headers and mlock.c, maybe more) - not a cleanup to get into now.
Quoted 5 lines
Quoted 5 lines
include/linux/rmap.h +2
-0atomic_inc (&page->_mapcount); + else +page_dup_compound_rmap (page ); }
...
Quoted 5 lines
Quoted 5 lines
mm/rmap.c +0
-1@@ -1176,20 +1157,16 @@ void page_dup_compound_rmap(struct page *page, bool compound)* Note that hugetlb does not call page_add_file_rmap(): * here is where hugetlb shared page mapcount is raised. */ -if (PageHuge (page)) {
Quoted 8 lines
mm/rmap.c void page_dup_compound_rmap(struct page *page, bool compound) · line 1162
Quoted 6 lines
mm/rmap.c +2
-3-atomic_inc (compound_mapcount_ptr (page)); -return ; - } +if (PageHuge (head)) { +atomic_inc (compound_mapcount_ptr (head));Remove the newline?
It was intentional there, I thought it was easier to read that way; but since this gets reverted in the next patch, I've no reason to fight over it - removed.
Hugh
PATCH 2/3 mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped
In reply to Hugh DickinsCan the lock_compound_mapcount() bit_spin_lock apparatus be removed now? Yes. Not by atomic64_t or cmpxchg games, those get difficult on 32-bit; but if we slightly abuse subpages_mapcount by additionally demanding that one bit be set there when the compound page is PMD-mapped, then a cascade of two atomic ops is able to maintain the stats without bit_spin_lock.
This is harder to reason about than when bit_spin_locked, but I believe safe; and no drift in stats detected when testing. When there are racing removes and adds, of course the sequence of operations is less well- defined; but each operation on subpages_mapcount is atomically good. What might be disastrous, is if subpages_mapcount could ever fleetingly appear negative: but the pte lock (or pmd lock) these rmap functions are called under, ensures that a last remove cannot race ahead of a first add.
Continue to make an exception for hugetlb (PageHuge) pages, though that exception can be easily removed by a further commit if necessary: leave subpages_mapcount 0, don't bother with COMPOUND_MAPPED in its case, just carry on checking compound_mapcount too in folio_mapped(), page_mapped().
Evidence is that this way goes slightly faster than the previous implementation in all cases (pmds after ptes now taking around 103ms); and relieves us of worrying about contention on the bit_spin_lock.
--- Documentation/mm/transhuge.rst | 7 +- include/linux/mm.h | 19 ++++- include/linux/rmap.h | 12 ++-- mm/debug.c | 2 +- mm/rmap.c | 124 +++++++-------------------------- 5 files changed, 52 insertions(+), 112 deletions(-)
Documentation/mm/transhuge.rst +3 -4
@@ -118,15 +118,14 @@ pages: succeeds on tail pages. - map/unmap of PMD entry for the whole compound page increment/decrement - ->compound_mapcount, stored in the first tail page of the compound page. + ->compound_mapcount, stored in the first tail page of the compound page; + and also increment/decrement ->subpages_mapcount (also in the first tail) + by COMPOUND_MAPPED when compound_mapcount goes from -1 to 0 or 0 to -1. - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement ->subpages_mapcount, stored in first tail page of the compound page, when _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. - In order to have race-free accounting of sub-pages mapped, changes to - sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are - are all locked by bit_spin_lock of PG_locked in the first tail ->flags. split_huge_page internally has to distribute the refcounts in the head page to the tail pages before clearing all PG_head/tail bits from the page
include/linux/mm.h +16 -3
@@ -828,7 +828,16 @@ static inline int head_compound_mapcount(struct page *head) }/* -* Number of sub-pages mapped by PTE, does not include compound mapcount. +* If a 16GB hugetlb page were mapped by PTEs of all of its 4kB sub-pages, +* its subpages_mapcount would be 0x400000: choose the COMPOUND_MAPPED bit +* above that range, instead of 2*(PMD_SIZE/PAGE_SIZE). Hugetlb currently +* leaves subpages_mapcount at 0, but avoid surprise if it participates later. +*/ +#define COMPOUND_MAPPED 0x800000 +#define SUBPAGES_MAPPED (COMPOUND_MAPPED - 1) + +/* +* Number of sub-pages mapped by PTE, plus COMPOUND_MAPPED if compound mapped. * Must be called only on head of compound page. */ static inline int head_subpages_mapcount (struct page *head)
@@ -893,8 +902,12 @@ static inline int total_mapcount(struct page *page)static inline bool folio_large_is_mapped (struct folio *folio) { -return atomic_read (folio_mapcount_ptr (folio)) + -atomic_read (folio_subpages_mapcount_ptr (folio)) >=0 ; +/* +* Reading folio_mapcount_ptr() below could be omitted if hugetlb +* participated in incrementing subpages_mapcount when compound mapped. +*/ +return atomic_read (folio_mapcount_ptr (folio)) >=0 || +atomic_read (folio_subpages_mapcount_ptr (folio)) >0 ; }/**
include/linux/rmap.h +6 -6
@@ -204,14 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -void page_dup_compound_rmap (struct page *page); +static inline void __page_dup_rmap (struct page *page,bool compound) +{ +atomic_inc (compound ?compound_mapcount_ptr (page) : &page->_mapcount); +}static inline void page_dup_file_rmap (struct page *page,bool compound) { -if (likely (!compound/* page is mapped by PTE */ )) -atomic_inc (&page->_mapcount); -else -page_dup_compound_rmap (page); +__page_dup_rmap (page, compound); }/**
@@ -260,7 +260,7 @@ static inline int page_try_dup_anon_rmap(struct page *page, bool compound,* the page R/O into both processes. */ dup: -page_dup_file_rmap (page, compound); +__page_dup_rmap (page, compound);return 0 ; }
mm/debug.c +1 -1
@@ -97,7 +97,7 @@ static void __dump_page(struct page *page)pr_warn ("head:%p order:%u compound_mapcount:%d subpages_mapcount:%d compound_pincount:%d\n" , head,compound_order (head),head_compound_mapcount (head), -head_subpages_mapcount (head), +head_subpages_mapcount (head) &SUBPAGES_MAPPED ,head_compound_pincount (head)); }
mm/rmap.c +26 -98
205 lines not on this page · raw message
Signature · 1 line
2.35.3
Re: [PATCH 2/3] mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped
Quoted 5 lines · Hugh Dickins
Can the
lock_compound_mapcount()bit_spin_lockapparatus be removed now? Yes. Not byatomic64_tor cmpxchg games, those get difficult on 32-bit; but if we slightly abusesubpages_mapcountby additionally demanding that one bit be set there when the compound page is PMD-mapped, then a cascade of two atomic ops is able to maintain the stats withoutbit_spin_lock.
Yay! New home for PageDoubleMap()! :P
Quoted 13 lines
This is harder to reason about than when
bit_spin_locked, but I believe safe; and no drift in stats detected when testing. When there are racing removes and adds, of course the sequence of operations is less well- defined; but each operation onsubpages_mapcountis atomically good. What might be disastrous, is ifsubpages_mapcountcould ever fleetingly appear negative: but the pte lock (or pmd lock) these rmap functions are called under, ensures that a last remove cannot race ahead of a first add.Continue to make an exception for hugetlb (PageHuge) pages, though that exception can be easily removed by a further commit if necessary: leave
subpages_mapcount0, don't bother withCOMPOUND_MAPPEDin its case, just carry on checkingcompound_mapcounttoo infolio_mapped(),page_mapped().
Quoted 5 lines
Evidence is that this way goes slightly faster than the previous implementation in all cases (pmds after ptes now taking around 103ms); and relieves us of worrying about contention on the
bit_spin_lock.Signed-off-by Hugh Dickins <[email protected]>
Jokes aside, looks neat.
As always few minor nits below.
Quoted 55 lines
--- Documentation/mm/transhuge.rst | 7 +- include/linux/mm.h | 19 ++++- include/linux/rmap.h | 12 ++-- mm/debug.c | 2 +- mm/rmap.c | 124 +++++++-------------------------- 5 files changed, 52 insertions(+), 112 deletions(-)Documentation/mm/transhuge.rst +3
-4@@ -118,15 +118,14 @@ pages: succeeds on tail pages. - map/unmap of PMD entry for the whole compound page increment/decrement - ->compound_mapcount, stored in the first tail page of the compound page. + ->compound_mapcount, stored in the first tail page of the compound page; + and also increment/decrement ->subpages_mapcount (also in the first tail) + by COMPOUND_MAPPED when compound_mapcount goes from -1 to 0 or 0 to -1. - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement ->subpages_mapcount, stored in first tail page of the compound page, when _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. - In order to have race-free accounting of sub-pages mapped, changes to - sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are - are all locked by bit_spin_lock of PG_locked in the first tail ->flags. split_huge_page internally has to distribute the refcounts in the head page to the tail pages before clearing all PG_head/tail bits from the pageinclude/linux/mm.h +10
-1@@ -828,7 +828,16 @@ static inline int head_compound_mapcount(struct page *head) }/* -* Number of sub-pages mapped by PTE, does not include compound mapcount. +* If a 16GB hugetlb page were mapped by PTEs of all of its 4kB sub-pages, +* its subpages_mapcount would be 0x400000: choose the COMPOUND_MAPPED bit +* above that range, instead of 2*(PMD_SIZE/PAGE_SIZE). Hugetlb currently +* leaves subpages_mapcount at 0, but avoid surprise if it participates later. +*/ +#define COMPOUND_MAPPED 0x800000 +#define SUBPAGES_MAPPED (COMPOUND_MAPPED - 1) + +/* +* Number of sub-pages mapped by PTE, plus COMPOUND_MAPPED if compound mapped. * Must be called only on head of compound page. */ static inline int head_subpages_mapcount (struct page *head)@@ -893,8 +902,12 @@ static inline int total_mapcount(struct page *page)
include/linux/mm.h static inline int total_mapcount(struct page *page) · line 910
Quoted 10 lines
include/linux/mm.h +6
-2static inline bool folio_large_is_mapped (struct folio *folio) { -return atomic_read (folio_mapcount_ptr (folio)) + -atomic_read (folio_subpages_mapcount_ptr (folio)) >=0 ; +/* +* Reading folio_mapcount_ptr() below could be omitted if hugetlb +* participated in incrementing subpages_mapcount when compound mapped. +*/ +return atomic_read (folio_mapcount_ptr (folio)) >=0 || +atomic_read (folio_subpages_mapcount_ptr (folio)) >0 ;
Maybe check folio_subpages_mapcount_ptr() first? It would avoid folio_mapcount_ptr() read for everything, but hugetlb.
Quoted 41 lines
include/linux/mm.h +0
-0}/** include/linux/rmap.h +6
-6@@ -204,14 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -void page_dup_compound_rmap (struct page *page); +static inline void __page_dup_rmap (struct page *page,bool compound) +{ +atomic_inc (compound ?compound_mapcount_ptr (page) : &page->_mapcount); +}static inline void page_dup_file_rmap (struct page *page,bool compound) { -if (likely (!compound/* page is mapped by PTE */ )) -atomic_inc (&page->_mapcount); -else -page_dup_compound_rmap (page); +__page_dup_rmap (page, compound); }/** @@ -260,7 +260,7 @@ static inline int page_try_dup_anon_rmap(struct page *page, bool compound,* the page R/O into both processes. */ dup: -page_dup_file_rmap (page, compound); +__page_dup_rmap (page, compound);return 0 ; }mm/debug.c +0
-0
mm/debug.c static void __dump_page(struct page *page) · line 100
Quoted 5 lines
mm/debug.c +1
-1@@ -97,7 +97,7 @@ static void __dump_page(struct page *page) pr_warn("head:%p order:%u compound_mapcount:%d subpages_mapcount:%d compound_pincount:%d\n", head, compound_order(head), head_compound_mapcount(head), - head_subpages_mapcount(head), + head_subpages_mapcount(head) & SUBPAGES_MAPPED,
Looks like applying the SUBPAGES_MAPPED mask belong to the head_subpages_mapcount() helper, not to the caller.
Quoted 225 lines
mm/debug.c +0
-0head_compound_pincount(head)); }mm/rmap.c +26
-98@@ -1085,38 +1085,6 @@ int pfn_mkclean_range(unsigned long pfn, unsigned long nr_pages, pgoff_t pgoff,return page_vma_mkclean_one (&pvmw); } -struct compound_mapcounts { -unsigned int compound_mapcount; -unsigned int subpages_mapcount; -}; - -/* -* lock_compound_mapcounts() first locks, then copies subpages_mapcount and -* compound_mapcount from head[1].compound_mapcount and subpages_mapcount, -* converting from struct page's internal representation to logical count -* (that is, adding 1 to compound_mapcount to hide its offset by -1). -*/ -static void lock_compound_mapcounts (struct page *head, -struct compound_mapcounts *local) -{ -bit_spin_lock (PG_locked, &head[1 ].flags); - local->compound_mapcount =atomic_read (compound_mapcount_ptr (head)) +1 ; - local->subpages_mapcount =atomic_read (subpages_mapcount_ptr (head)); -} - -/* -* After caller has updated subpage._mapcount, local subpages_mapcount and -* local compound_mapcount, as necessary, unlock_compound_mapcounts() converts -* and copies them back to the compound head[1] fields, and then unlocks. -*/ -static void unlock_compound_mapcounts (struct page *head, -struct compound_mapcounts *local) -{ -atomic_set (compound_mapcount_ptr (head), local->compound_mapcount -1 ); -atomic_set (subpages_mapcount_ptr (head), local->subpages_mapcount); -bit_spin_unlock (PG_locked, &head[1 ].flags); -} -int total_compound_mapcount (struct page *head) {int mapcount =head_compound_mapcount (head);@@ -1124,7 +1092,7 @@ int total_compound_mapcount(struct page *head)int i;/* In the common case, avoid the loop when no subpages mapped by PTE */ -if (head_subpages_mapcount (head) ==0 ) +if ((head_subpages_mapcount (head) &SUBPAGES_MAPPED ) ==0 )return mapcount;/* * Add all the PTE mappings of those subpages mapped by PTE. @@ -1140,35 +1108,6 @@ int total_compound_mapcount(struct page *head)return mapcount; } -/* -* page_dup_compound_rmap(), used when copying mm, -* provides a simple example of using lock_ and unlock_compound_mapcounts(). -*/ -void page_dup_compound_rmap (struct page *head) -{ -struct compound_mapcounts mapcounts; - -/* -* Hugetlb pages could use lock_compound_mapcounts(), like THPs do; -* but at present they are still being managed by atomic operations: -* which are likely to be somewhat faster, so don't rush to convert -* them over without evaluating the effect. -* -* Note that hugetlb does not call page_add_file_rmap(): -* here is where hugetlb shared page mapcount is raised. -*/ -if (PageHuge (head)) { -atomic_inc (compound_mapcount_ptr (head)); - - }else if (PageTransHuge (head)) { -/* That test is redundant: it's for safety or to optimize out */ - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.compound_mapcount++; -unlock_compound_mapcounts (head, &mapcounts); - } -} -/** * page_move_anon_rmap - move a page to our anon_vma * @page: the page to move to our anon_vma @@ -1278,7 +1217,7 @@ static void __page_check_anon_rmap(struct page *page,void page_add_anon_rmap (struct page *page,struct vm_area_struct *vma,unsigned long address,rmap_t flags) { -struct compound_mapcounts mapcounts; +atomic_t *mapped;int nr =0 , nr_pmdmapped =0 ;bool compound = flags &RMAP_COMPOUND ;bool first;@@ -1290,24 +1229,20 @@ void page_add_anon_rmap(struct page *page, first =atomic_inc_and_test (&page->_mapcount); nr = first;if (first &&PageCompound (page)) { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount++; - nr = !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); + mapped =subpages_mapcount_ptr (compound_head (page)); + nr =atomic_inc_return_relaxed (mapped); + nr = !(nr &COMPOUND_MAPPED ); } }else if (PageTransHuge (page)) {/* That test is redundant: it's for safety or to optimize out */ -lock_compound_mapcounts (page, &mapcounts); - first = !mapcounts.compound_mapcount; - mapcounts.compound_mapcount++; + first =atomic_inc_and_test (compound_mapcount_ptr (page));if (first) { + mapped =subpages_mapcount_ptr (page); + nr =atomic_add_return_relaxed (COMPOUND_MAPPED , mapped); nr_pmdmapped =thp_nr_pages (page); - nr = nr_pmdmapped - mapcounts.subpages_mapcount; + nr = nr_pmdmapped - (nr &SUBPAGES_MAPPED ); } -unlock_compound_mapcounts (page, &mapcounts); }VM_BUG_ON_PAGE (!first && (flags &RMAP_EXCLUSIVE ), page);@@ -1360,6 +1295,7 @@ void page_add_new_anon_rmap(struct page *page,VM_BUG_ON_PAGE (!PageTransHuge (page), page);/* increment count (starts at -1) */ atomic_set (compound_mapcount_ptr (page),0 ); +atomic_set (subpages_mapcount_ptr (page),COMPOUND_MAPPED ); nr =thp_nr_pages (page);__mod_lruvec_page_state (page,NR_ANON_THPS , nr); }@@ -1379,7 +1315,7 @@ void page_add_new_anon_rmap(struct page *page,void page_add_file_rmap (struct page *page,struct vm_area_struct *vma,bool compound) { -struct compound_mapcounts mapcounts; +atomic_t *mapped;int nr =0 , nr_pmdmapped =0 ;bool first;@@ -1390,24 +1326,20 @@ void page_add_file_rmap(struct page *page, first =atomic_inc_and_test (&page->_mapcount); nr = first;if (first &&PageCompound (page)) { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount++; - nr = !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); + mapped =subpages_mapcount_ptr (compound_head (page)); + nr =atomic_inc_return_relaxed (mapped); + nr = !(nr &COMPOUND_MAPPED ); } }else if (PageTransHuge (page)) {/* That test is redundant: it's for safety or to optimize out */ -lock_compound_mapcounts (page, &mapcounts); - first = !mapcounts.compound_mapcount; - mapcounts.compound_mapcount++; + first =atomic_inc_and_test (compound_mapcount_ptr (page));if (first) { + mapped =subpages_mapcount_ptr (page); + nr =atomic_add_return_relaxed (COMPOUND_MAPPED , mapped); nr_pmdmapped =thp_nr_pages (page); - nr = nr_pmdmapped - mapcounts.subpages_mapcount; + nr = nr_pmdmapped - (nr &SUBPAGES_MAPPED ); } -unlock_compound_mapcounts (page, &mapcounts); }if (nr_pmdmapped)@@ -1431,7 +1363,7 @@ void page_add_file_rmap(struct page *page,void page_remove_rmap (struct page *page,struct vm_area_struct *vma,bool compound) { -struct compound_mapcounts mapcounts; +atomic_t *mapped;int nr =0 , nr_pmdmapped =0 ;bool last;@@ -1451,24 +1383,20 @@ void page_remove_rmap(struct page *page, last =atomic_add_negative (-1 , &page->_mapcount); nr = last;if (last &&PageCompound (page)) { -struct page *head =compound_head (page); - -lock_compound_mapcounts (head, &mapcounts); - mapcounts.subpages_mapcount--; - nr = !mapcounts.compound_mapcount; -unlock_compound_mapcounts (head, &mapcounts); + mapped =subpages_mapcount_ptr (compound_head (page)); + nr =atomic_dec_return_relaxed (mapped); + nr = !(nr &COMPOUND_MAPPED ); } }else if (PageTransHuge (page)) {/* That test is redundant: it's for safety or to optimize out */ -lock_compound_mapcounts (page, &mapcounts); - mapcounts.compound_mapcount--; - last = !mapcounts.compound_mapcount; + last =atomic_add_negative (-1 ,compound_mapcount_ptr (page));if (last) { + mapped =subpages_mapcount_ptr (page); + nr =atomic_sub_return_relaxed (COMPOUND_MAPPED , mapped); nr_pmdmapped =thp_nr_pages (page); - nr = nr_pmdmapped - mapcounts.subpages_mapcount; + nr = nr_pmdmapped - (nr &SUBPAGES_MAPPED ); } -unlock_compound_mapcounts (page, &mapcounts); }if (nr_pmdmapped) {Signature · 1 line
2.35.3
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 2/3] mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped
Quoted 8 lines · Kirill A. Shutemov
Quoted 5 lines · Hugh Dickins
Can the
lock_compound_mapcount()bit_spin_lockapparatus be removed now? Yes. Not byatomic64_tor cmpxchg games, those get difficult on 32-bit; but if we slightly abusesubpages_mapcountby additionally demanding that one bit be set there when the compound page is PMD-mapped, then a cascade of two atomic ops is able to maintain the stats withoutbit_spin_lock.Yay! New home for
PageDoubleMap()! :P
:) You only asked for one bit for PageDoubleMap, I've been greedier; so it's not surprising if it has worked out better now.
...
Quoted 3 lines
Jokes aside, looks neat.
Thanks; but I'm very glad that Linus expressed his dissatisfaction with the first implementation, this one does feel much better.
Quoted 2 lines
As always few minor nits below.
...
Quoted 15 lines
include/linux/mm.h static inline int total_mapcount(struct page *page) · line 910
Quoted 12 lines
include/linux/mm.h +6
-2@@ -893,8 +902,12 @@ static inline int total_mapcount(struct page *page)static inline bool folio_large_is_mapped (struct folio *folio) { -return atomic_read (folio_mapcount_ptr (folio)) + -atomic_read (folio_subpages_mapcount_ptr (folio)) >=0 ; +/* +* Reading folio_mapcount_ptr() below could be omitted if hugetlb +* participated in incrementing subpages_mapcount when compound mapped. +*/ +return atomic_read (folio_mapcount_ptr (folio)) >=0 || +atomic_read (folio_subpages_mapcount_ptr (folio)) >0 ;Maybe check
folio_subpages_mapcount_ptr()first? It would avoidfolio_mapcount_ptr()read for everything, but hugetlb.
Okay: I'm not convinced, but don't mind switching those around: done.
Quoted 11 lines
mm/debug.c static void __dump_page(struct page *page) · line 100
Quoted 8 lines
mm/debug.c +1
-1@@ -97,7 +97,7 @@ static void __dump_page(struct page *page) pr_warn("head:%p order:%u compound_mapcount:%d subpages_mapcount:%d compound_pincount:%d\n", head, compound_order(head), head_compound_mapcount(head), - head_subpages_mapcount(head), + head_subpages_mapcount(head) & SUBPAGES_MAPPED,Looks like applying the
SUBPAGES_MAPPEDmask belong to thehead_subpages_mapcount()helper, not to the caller.
Yes, that would be more consistent, helper function doing the massage. Done. __dump_page() then remains unchanged, but free_tail_pages_check() uses subpages_mapcount_ptr(head_page) to check the whole field is zero.
v2 coming up - thanks.
Hugh
PATCH 3/3 mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
In reply to Hugh DickinsIt's hard to add a page_add_anon_rmap() into __split_huge_pmd_locked()'s HPAGE_PMD_NR set_pte_at() loop, without wincing at the "freeze" case's HPAGE_PMD_NR page_remove_rmap() loop below it.
It's just a mistake to add rmaps in the "freeze" (insert migration entries prior to splitting huge page) case: the pmd_migration case already avoids doing that, so just follow its lead. page_add_ref() versus put_page() likewise. But why is one more put_page() needed in the "freeze" case? Because it's removing the pmd rmap, already removed when pmd_migration (and freeze and pmd_migration are mutually exclusive cases).
--- mm/huge_memory.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-)
mm/huge_memory.c +5 -10
@@ -2135,7 +2135,6 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, uffd_wp =pmd_uffd_wp (old_pmd);VM_BUG_ON_PAGE (!page_count (page), page); -page_ref_add (page,HPAGE_PMD_NR -1 );/* * Without "freeze", we'll simply split the PMD, propagating the
@@ -2155,6 +2154,8 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, anon_exclusive =PageAnon (page) &&PageAnonExclusive (page);if (freeze && anon_exclusive &&page_try_share_anon_rmap (page)) freeze = false; +if (!freeze) +page_ref_add (page,HPAGE_PMD_NR -1 ); }/*
@@ -2210,27 +2211,21 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, entry =pte_mksoft_dirty (entry);if (uffd_wp) entry =pte_mkuffd_wp (entry); +page_add_anon_rmap (page + i, vma, addr, false); } pte =pte_offset_map (&_pmd, addr);BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry); -if (!pmd_migration) -page_add_anon_rmap (page + i, vma, addr, false);pte_unmap (pte); }if (!pmd_migration)page_remove_rmap (page, vma, true); +if (freeze) +put_page (page);smp_wmb ();/* make pte visible before pmd */ pmd_populate (mm, pmd, pgtable); - -if (freeze) { -for (i =0 ; i <HPAGE_PMD_NR ; i++) { -page_remove_rmap (page + i, vma, false); -put_page (page + i); - } - } } void __split_huge_pmd(struct vm_area_struct *vma, pmd_t *pmd,
Signature · 1 line
2.35.3
Re: [PATCH 3/3] mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
Quoted 4 lines · Hugh Dickins
It's hard to add a
page_add_anon_rmap()into __split_huge_pmd_locked()'sHPAGE_PMD_NRset_pte_at()loop, without wincing at the "freeze" case'sHPAGE_PMD_NRpage_remove_rmap()loop below it.
Quoted 8 lines
It's just a mistake to add rmaps in the "freeze" (insert migration entries prior to splitting huge page) case: the
pmd_migrationcase already avoids doing that, so just follow its lead.page_add_ref()versusput_page()likewise. But why is one moreput_page()needed in the "freeze" case? Because it's removing the pmd rmap, already removed whenpmd_migration(and freeze andpmd_migrationare mutually exclusive cases).Signed-off-by Hugh Dickins <[email protected]>
Signature · 1 line
Kiryl Shutsemau / Kirill A. Shutemov
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Hugh DickinsQuoted 5 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.
This looks good to me. Particularly 2/3 made me go "Aww, yes" but the overall line removal stats look good too.
That said, I only looked at the patches, and not the end result itself. But not having the bit spin lock is, I think, a huge improvement.
I do wonder if this should be now just merged with your previous series - it looks a bit odd how your previous series adds that bitlock, only for it to be immediately removed.
But if you think the logic ends up being easier to follow this way as two separate patch series, I guess I don't care.
And the memcg locking is entirely a separate issue, and I hope Johannes will deal with that.
Thanks,
Linus
Johannes Weiner
reviewerRe: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 18 lines · Linus Torvalds
Quoted 5 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.This looks good to me. Particularly 2/3 made me go "Aww, yes" but the overall line removal stats look good too.
That said, I only looked at the patches, and not the end result itself. But not having the bit spin lock is, I think, a huge improvement.
I do wonder if this should be now just merged with your previous series - it looks a bit odd how your previous series adds that bitlock, only for it to be immediately removed.
Quoted 5 lines
But if you think the logic ends up being easier to follow this way as two separate patch series, I guess I don't care.
And the memcg locking is entirely a separate issue, and I hope Johannes will deal with that.
Yeah, I'll redo the removal on top of this series and resend it.
Thanks
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Linus TorvaldsQuoted 7 lines · Linus Torvalds
Quoted 5 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.
Quoted 6 lines
This looks good to me. Particularly 2/3 made me go "Aww, yes" but the overall line removal stats look good too.
That said, I only looked at the patches, and not the end result itself. But not having the bit spin lock is, I think, a huge improvement.
Great, thanks a lot for looking through.
Quoted 7 lines
I do wonder if this should be now just merged with your previous series - it looks a bit odd how your previous series adds that bitlock, only for it to be immediately removed.
But if you think the logic ends up being easier to follow this way as two separate patch series, I guess I don't care.
I rather like having its evolution on record there, but that might just be my sentimentality + laziness. Kirill did a grand job of reviewing the first series: I think that, at least for now, it would be easier for people to review the changes if the two series are not recombined.
But the first series has not yet graduated from mm-unstable, so if Andrew and/or Kirill also prefer to have them combined into one bit_spin_lock-less series, that I can do. (And the end result should be identical, so would not complicate Johannes's lock_page_memcg() excision.)
Hugh
Quoted 6 lines
And the memcg locking is entirely a separate issue, and I hope Johannes will deal with that.
Thanks,
Linus
Andrew Morton
maintainerRe: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 4 lines · On Fri, 18 Nov 2022 12:51:09 -0800 (PST) Hugh Dickins <[email protected]> wrote:
But the first series has not yet graduated from mm-unstable, so if Andrew and/or Kirill also prefer to have them combined into one bit_spin_lock-less series, that I can do. (And the end result should be identical, so would not complicate Johannes's
lock_page_memcg()excision.)
I'd prefer that approach. It's -rc5 and the earlier "mm,huge,rmap:
unify and speed up compound mapcounts" series has had some testing. I'd prefer not to toss it all out and start again.
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 2 lines · Andrew Morton
I'd prefer that approach.
The "that approach" is a bit ambiguous here, particularly considering how you quoted things.
But I think from the context you meant "keep them as two separate series, even if the second undoes part of the first and does it differently".
And that's fine. Even if it's maybe a bit odd to introduce that locking that then goes away, I can't argue with "the first series was already reviewed and has gone through a fair amount of testing".
Linus
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Andrew MortonQuoted 8 lines · Andrew Morton
Quoted 4 lines · On Fri, 18 Nov 2022 12:51:09 -0800 (PST) Hugh Dickins <[email protected]> wrote:
But the first series has not yet graduated from mm-unstable, so if Andrew and/or Kirill also prefer to have them combined into one bit_spin_lock-less series, that I can do. (And the end result should be identical, so would not complicate Johannes's
lock_page_memcg()excision.)I'd prefer that approach.
I think you're saying that you prefer the other approach, to keep the two series separate (second immediately after the first, or not, doesn't matter), rather than combined into one bit_spin_lock-less series. Please clarify! Thanks,
Hugh
Quoted 3 lines
It's -rc5 and the earlier "mm,huge,rmap:
unify and speed up compound mapcounts" series has had some testing. I'd prefer not to toss it all out and start again.
Andrew Morton
maintainerRe: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 8 lines · On Fri, 18 Nov 2022 14:10:32 -0800 (PST) Hugh Dickins <[email protected]> wrote:
Quoted 7 lines · Andrew Morton
Quoted 4 lines · On Fri, 18 Nov 2022 12:51:09 -0800 (PST) Hugh Dickins <[email protected]> wrote:
But the first series has not yet graduated from mm-unstable, so if Andrew and/or Kirill also prefer to have them combined into one bit_spin_lock-less series, that I can do. (And the end result should be identical, so would not complicate Johannes's
lock_page_memcg()excision.)
Quoted 6 lines
Quoted 1 line
I'd prefer that approach.
I think you're saying that you prefer the other approach, to keep the two series separate (second immediately after the first, or not, doesn't matter), rather than combined into one bit_spin_lock-less series. Please clarify! Thanks,
Yes, two separate series. Apologies for the confuddling.
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Hugh DickinsQuoted 5 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.
Is there a plan to remove lock_page_memcg() altogether which I missed? I am planning to make lock_page_memcg() a nop for cgroup-v2 (as it shows up in the perf profile on exit path) but if we are removing it then I should just wait.
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 4 lines · Shakeel Butt
Is there a plan to remove
lock_page_memcg()altogether which I missed? I am planning to makelock_page_memcg()a nop for cgroup-v2 (as it shows up in the perf profile on exit path)
Yay. It seems I'm not the only one hating it.
Quoted 1 line
but if we are removing it then I should just wait.
Well, I think Johannes was saying that at least the case I disliked (the rmap removal from the page table tear-down - I strongly suspect it's the one you're seeing on your perf profile too) can be removed entirely as long as it's done under the page table lock (which my final version of the rmap delaying still was).
See
https://lore.kernel.org/all/Y2llcRiDLHc2kg%[email protected]/
for his preliminary patch.
That said, if you have some patch to make it a no-op for _other_ reasons, and could be done away with _entirely_ (not just for rmap), then that would be even better. I am not a fan of that lock in general, but in the teardown rmap path it's actively horrifying because it is taken one page at a time. So it's taken a *lot* (although you might not see it if all you run is long-running benchmarks - it's mainly the "run lots of small scripts that really hits it).
The reason it seems to be so horrifyingly noticeable on the exit path is that the fork() side already does the rmap stuff (mainly __page_dup_rmap()) _without_ having to do the lock_page_memcg() dance.
So I really hate that lock. It's completely inconsistent, and it all feels very wrong. It seemed entirely pointless when I was looking at the rmap removal path for a single page. The fact that both you and Johannes seem to be more than ready to just remove it makes me much happier, because I've never actually known the memcg code enough to do anything about my simmering hatred.
Linus
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 6 lines · Linus Torvalds
Quoted 4 lines · Shakeel Butt
Is there a plan to remove
lock_page_memcg()altogether which I missed? I am planning to makelock_page_memcg()a nop for cgroup-v2 (as it shows up in the perf profile on exit path)
Quoted 7 lines
Yay. It seems I'm not the only one hating it.
Quoted 1 line
but if we are removing it then I should just wait.
Well, I think Johannes was saying that at least the case I disliked (the rmap removal from the page table tear-down - I strongly suspect it's the one you're seeing on your perf profile too)
Yes indeed that is the one.
- 99.89% 0.00% fork-large-mmap [kernel.kallsyms] [k] entry_SYSCALL_64_after_hw◆
entry_SYSCALL_64_after_hwframe
- do_syscall_64
- 48.94% __x64_sys_exit_group
do_group_exit
- do_exit
- 48.94% exit_mm
mmput
- __mmput
- exit_mmap
- 48.61% unmap_vmas
- 48.61% unmap_single_vma
- unmap_page_range
- 48.60% zap_p4d_range
- 44.66% zap_pte_range
+ 12.61% tlb_flush_mmu
- 9.38% page_remove_rmap 2.50% lock_page_memcg 2.37% unlock_page_memcg 0.61% PageHuge 4.80% vm_normal_page 2.56% __tlb_remove_page_size 0.85% lock_page_memcg 0.53% PageHuge
2.22% __tlb_remove_page_size 0.93% vm_normal_page 0.72% page_remove_rmap
Quoted 6 lines
can be removed
entirely as long as it's done under the page table lock (which my final version of the rmap delaying still was).See
Quoted 7 lines
https://lore.kernel.org/all/Y2llcRiDLHc2kg%[email protected]/
for his preliminary patch.
That said, if you have some patch to make it a no-op for _other_ reasons, and could be done away with _entirely_ (not just for rmap), then that would be even better.
I am actually looking at deprecating the whole "move charge" funcitonality of cgroup-v1 i.e. the underlying reason lock_page_memcg exists. That already does not work for couple of cases like partially mapped THP and madv_free'd pages. Though that deprecation process would take some time. In the meantime I was looking at if we can make these functions nop for cgroup-v2.
thanks,
Shakeel
Johannes Weiner
reviewerRe: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Shakeel ButtQuoted 10 lines · Shakeel Butt
Quoted 4 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.Is there a plan to remove
lock_page_memcg()altogether which I missed? I am planning to makelock_page_memcg()a nop for cgroup-v2 (as it shows up in the perf profile on exit path) but if we are removing it then I should just wait.
We can remove it for rmap at least, but we might be able to do more.
Besides rmap, we're left with the dirty and writeback page transitions that wrt cgroups need to be atomic with NR_FILE_DIRTY and NR_WRITEBACK.
Looking through the various callsites, I think we can delete it from setting and clearing dirty state, as we always hold the page lock (or the pte lock in some instances of folio_mark_dirty). Both of these are taken from the cgroup side, so we're good there.
I think we can also remove it when setting writeback, because those sites have the page locked as well.
That leaves clearing writeback. This can't hold the page lock due to the atomic context, so currently we need to take lock_page_memcg() as the lock of last resort.
I wonder if we can have cgroup take the xalock instead: writeback ending on file pages always acquires the xarray lock. Swap writeback currently doesn't, but we could make it so (swap_address_space).
The only thing that gives me pause is the !mapping check in __folio_end_writeback. File and swapcache pages usually have mappings, and truncation waits for writeback to finish before axing page->mapping. So AFAICS this can only happen if we call end_writeback on something that isn't under writeback - in which case the test_clear will fail and we don't update the stats anyway. But I want to be sure.
Does anybody know from the top of their heads if a page under writeback could be without a mapping in some weird cornercase?
If we could ensure that the NR_WRITEBACK decs are always protected by the xalock, we could grab it from mem_cgroup_move_account(), and then kill lock_page_memcg() altogether.
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 7 lines · Johannes Weiner
Quoted 6 lines · Shakeel Butt
Quoted 4 lines · Hugh Dickins
Linus was underwhelmed by the earlier compound mapcounts series:
this series builds on top of it (as in next-20221117) to follow up on his suggestions - exceptrmap.cstill usinglock_page_memcg(), since I hesitate to steal the pleasure of deletion from Johannes.
Quoted 6 lines
Quoted 4 lines
Is there a plan to remove
lock_page_memcg()altogether which I missed? I am planning to makelock_page_memcg()a nop for cgroup-v2 (as it shows up in the perf profile on exit path) but if we are removing it then I should just wait.We can remove it for rmap at least, but we might be able to do more.
I hope the calls from mm/rmap.c can be deleted before deciding the bigger picture for lock_page_memcg() itself; getting rid of it would be very nice, but it has always had a difficult job to do (and you've devoted lots of good effort to minimizing it).
Quoted 12 lines
Besides rmap, we're left with the dirty and writeback page transitions that wrt cgroups need to be atomic with
NR_FILE_DIRTYandNR_WRITEBACK.Looking through the various callsites, I think we can delete it from setting and clearing dirty state, as we always hold the page lock (or the pte lock in some instances of
folio_mark_dirty). Both of these are taken from the cgroup side, so we're good there.I think we can also remove it when setting writeback, because those sites have the page locked as well.
Quoted 7 lines
That leaves clearing writeback. This can't hold the page lock due to the atomic context, so currently we need to take
lock_page_memcg()as the lock of last resort.I wonder if we can have cgroup take the xalock instead: writeback ending on file pages always acquires the xarray lock. Swap writeback currently doesn't, but we could make it so (
swap_address_space).
It's a little bit of a regression to have to take that lock when ending writeback on swap (compared with the rcu_read_lock() of almost every lock_page_memcg()); but I suppose if swap had been doing that all along, like the normal page cache case, I would not be complaining.
Quoted 10 lines
The only thing that gives me pause is the !mapping check in
__folio_end_writeback. File and swapcache pages usually have mappings, and truncation waits for writeback to finish before axingpage->mapping. So AFAICS this can only happen if we callend_writebackon something that isn't under writeback - in which case thetest_clearwill fail and we don't update the stats anyway. But I want to be sure.Does anybody know from the top of their heads if a page under writeback could be without a mapping in some weird cornercase?
End of writeback has been a persistent troublemaker, in several ways; I forget whether we are content with it now or not.
I would not trust whatever I think OTOH of that !mapping case, but I was deeper into it two years ago, and find myself saying "Can mapping be NULL? I don't see how, but allow for that with a WARN_ON_ONCE()" in a patch I posted then (but it didn't go in, we went in another direction).
I'm pretty sure it never warned once for me, but I probably wasn't doing enough to test it. And IIRC I did also think that the !mapping check had perhaps been copied from a related function, one where it made more sense.
It's also worth noting that the two stats which get decremented there, NR_WRITEBACK and NR_ZONE_WRITE_PENDING, are two of the three which we have commented "Skip checking stats known to go negative occasionally" in mm/vmstat.c: I never did come up with a convincing explanation for that (Roman had his explanation, but I wasn't quite convinced). Maybe it would just be wrong to touch them if mapping were NULL.
Quoted 4 lines
If we could ensure that the
NR_WRITEBACKdecs are always protected by the xalock, we could grab it frommem_cgroup_move_account(), and then killlock_page_memcg()altogether.
I suppose so (but I still feel grudging about the xalock for swap).
Hugh
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
In reply to Johannes WeinerQuoted 15 lines · Johannes Weiner
That leaves clearing writeback. This can't hold the page lock due to the atomic context, so currently we need to take
lock_page_memcg()as the lock of last resort.I wonder if we can have cgroup take the xalock instead: writeback ending on file pages always acquires the xarray lock. Swap writeback currently doesn't, but we could make it so (
swap_address_space).The only thing that gives me pause is the !mapping check in
__folio_end_writeback. File and swapcache pages usually have mappings, and truncation waits for writeback to finish before axingpage->mapping. So AFAICS this can only happen if we callend_writebackon something that isn't under writeback - in which case thetest_clearwill fail and we don't update the stats anyway. But I want to be sure.
Quoted 2 lines
Does anybody know from the top of their heads if a page under writeback could be without a mapping in some weird cornercase?
I can't think of such a corner case. We should always wait for writeback to finish before removing the page from the page cache; the writeback bit used to be (and kind of still is) an implicit reference to the page, which means that we can't remove the page cache's reference to the page without waiting for writeback.
Quoted 3 lines
If we could ensure that the
NR_WRITEBACKdecs are always protected by the xalock, we could grab it frommem_cgroup_move_account(), and then killlock_page_memcg()altogether.
I'm not thrilled by this idea, but I'm not going to veto it.
Johannes Weiner
reviewerRe: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 16 lines · Matthew Wilcox
Quoted 15 lines · Johannes Weiner
That leaves clearing writeback. This can't hold the page lock due to the atomic context, so currently we need to take
lock_page_memcg()as the lock of last resort.I wonder if we can have cgroup take the xalock instead: writeback ending on file pages always acquires the xarray lock. Swap writeback currently doesn't, but we could make it so (
swap_address_space).The only thing that gives me pause is the !mapping check in
__folio_end_writeback. File and swapcache pages usually have mappings, and truncation waits for writeback to finish before axingpage->mapping. So AFAICS this can only happen if we callend_writebackon something that isn't under writeback - in which case thetest_clearwill fail and we don't update the stats anyway. But I want to be sure.
Quoted 8 lines
Quoted 2 lines
Does anybody know from the top of their heads if a page under writeback could be without a mapping in some weird cornercase?
I can't think of such a corner case. We should always wait for writeback to finish before removing the page from the page cache; the writeback bit used to be (and kind of still is) an implicit reference to the page, which means that we can't remove the page cache's reference to the page without waiting for writeback.
Great, thanks!
Quoted 5 lines
Quoted 3 lines
If we could ensure that the
NR_WRITEBACKdecs are always protected by the xalock, we could grab it frommem_cgroup_move_account(), and then killlock_page_memcg()altogether.I'm not thrilled by this idea, but I'm not going to veto it.
Ok, I'm also happy to drop this one.
Certainly, the rmap one is the lowest-hanging fruit. I have the patch rebased against Hugh's series in mm-unstable; I'll wait for that to settle down, and then send an updated version to Andrew.
Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount
Quoted 32 lines · Johannes Weiner
Quoted 16 lines · Matthew Wilcox
Quoted 15 lines · Johannes Weiner
That leaves clearing writeback. This can't hold the page lock due to the atomic context, so currently we need to take
lock_page_memcg()as the lock of last resort.I wonder if we can have cgroup take the xalock instead: writeback ending on file pages always acquires the xarray lock. Swap writeback currently doesn't, but we could make it so (
swap_address_space).The only thing that gives me pause is the !mapping check in
__folio_end_writeback. File and swapcache pages usually have mappings, and truncation waits for writeback to finish before axingpage->mapping. So AFAICS this can only happen if we callend_writebackon something that isn't under writeback - in which case thetest_clearwill fail and we don't update the stats anyway. But I want to be sure.Quoted 8 lines
Quoted 2 lines
Does anybody know from the top of their heads if a page under writeback could be without a mapping in some weird cornercase?
I can't think of such a corner case. We should always wait for writeback to finish before removing the page from the page cache; the writeback bit used to be (and kind of still is) an implicit reference to the page, which means that we can't remove the page cache's reference to the page without waiting for writeback.
Great, thanks!
Quoted 4 lines
Quoted 3 lines
If we could ensure that the
NR_WRITEBACKdecs are always protected by the xalock, we could grab it frommem_cgroup_move_account(), and then killlock_page_memcg()altogether.
Quoted 7 lines
Quoted 1 line
I'm not thrilled by this idea, but I'm not going to veto it.
Ok, I'm also happy to drop this one.
Certainly, the rmap one is the lowest-hanging fruit. I have the patch rebased against Hugh's series in mm-unstable; I'll wait for that to settle down, and then send an updated version to Andrew.
I am planning to initiate the deprecation of the move charge functionality of v1. So I would say let's go with low hanging fruit for now and let slow process of deprecation remove the remaining cases.
v2 cover mm,thp,rmap: rework the use of subpages_mapcount
In reply to Hugh DickinsAndrew, please replace the 1/3, 1/3 fix, 2/3, 3/3 in mm-unstable by these v2 three: which incorporate the uninitialized warning fix, and adjustments according to Kirill's review comments, plus his Acks - I couldn't quite manage them just by -fixes.
No functional change from the v1 series.
1/3 mm,thp,rmap: subpages_mapcount of PTE-mapped subpages 2/3 mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped 3/3 mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
Documentation/mm/transhuge.rst | 10 +- include/linux/mm.h | 67 +++++++---- include/linux/rmap.h | 12 +- mm/huge_memory.c | 15 +-- mm/page_alloc.c | 2 +- mm/rmap.c | 219 ++++++++++------------------------- 6 files changed, 124 insertions(+), 201 deletions(-)
Thanks!
Hugh
PATCH v2 1/3 mm,thp,rmap: subpages_mapcount of PTE-mapped subpages
Following suggestion from Linus, instead of counting every PTE map of a compound page in subpages_mapcount, just count how many of its subpages are PTE-mapped: this yields the exact number needed for NR_ANON_MAPPED and NR_FILE_MAPPED stats, without any need for a locked scan of subpages; and requires updating the count less often.
This does then revert total_mapcount() and folio_mapcount() to needing a scan of subpages; but they are inherently racy, and need no locking, so Linus is right that the scans are much better done there. Plus (unlike in 6.1 and previous) subpages_mapcount lets us avoid the scan in the common case of no PTE maps. And page_mapped() and folio_mapped() remain scanless and just as efficient with the new meaning of subpages_mapcount:
those are the functions which I most wanted to remove the scan from.
The updated page_dup_compound_rmap() is no longer suitable for use by anon THP's __split_huge_pmd_locked(); but page_add_anon_rmap() can be used for that, so long as its VM_BUG_ON_PAGE(!PageLocked) is deleted.
Evidence is that this way goes slightly faster than the previous implementation for most cases; but significantly faster in the (now scanless) pmds after ptes case, which started out at 870ms and was brought down to 495ms by the previous series, now takes around 105ms.
---
v2: fix uninitialized 'first', reported by Yu Zhao and Dan Carpenter
moved "mapped by PTE" comments above the !compound tests, per Kirill removed a newline (which goes away in the next patch), per Kirill
Documentation/mm/transhuge.rst | 3 +- include/linux/mm.h | 52 ++++++----- include/linux/rmap.h | 9 +- mm/huge_memory.c | 2 +- mm/rmap.c | 160 ++++++++++++++------------------- 5 files changed, 107 insertions(+), 119 deletions(-)
Documentation/mm/transhuge.rst +2 -1
@@ -122,7 +122,8 @@ pages: - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement - ->subpages_mapcount, stored in first tail page of the compound page. + ->subpages_mapcount, stored in first tail page of the compound page, when + _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. In order to have race-free accounting of sub-pages mapped, changes to sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are are all locked by bit_spin_lock of PG_locked in the first tail ->flags.
include/linux/mm.h +31 -21
76 lines not on this page · raw message
include/linux/rmap.h +5 -4
@@ -204,14 +204,15 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -void page_dup_compound_rmap (struct page *page,bool compound); +void page_dup_compound_rmap (struct page *page);static inline void page_dup_file_rmap (struct page *page,bool compound) { -if (PageCompound (page)) -page_dup_compound_rmap (page, compound); -else +/* Is page being mapped by PTE? */ +if (likely (!compound))atomic_inc (&page->_mapcount); +else +page_dup_compound_rmap (page); }/**
mm/huge_memory.c +1 -1
@@ -2215,7 +2215,7 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd,BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry);if (!pmd_migration) -page_dup_compound_rmap (page + i, false); +page_add_anon_rmap (page + i, vma, addr, false);pte_unmap (pte); }
mm/rmap.c +68 -92
235 lines not on this page · raw message
Signature · 1 line
2.35.3
PATCH v2 2/3 mm,thp,rmap: subpages_mapcount COMPOUND_MAPPED if PMD-mapped
In reply to Hugh DickinsCan the lock_compound_mapcount() bit_spin_lock apparatus be removed now? Yes. Not by atomic64_t or cmpxchg games, those get difficult on 32-bit; but if we slightly abuse subpages_mapcount by additionally demanding that one bit be set there when the compound page is PMD-mapped, then a cascade of two atomic ops is able to maintain the stats without bit_spin_lock.
This is harder to reason about than when bit_spin_locked, but I believe safe; and no drift in stats detected when testing. When there are racing removes and adds, of course the sequence of operations is less well- defined; but each operation on subpages_mapcount is atomically good. What might be disastrous, is if subpages_mapcount could ever fleetingly appear negative: but the pte lock (or pmd lock) these rmap functions are called under, ensures that a last remove cannot race ahead of a first add.
Continue to make an exception for hugetlb (PageHuge) pages, though that exception can be easily removed by a further commit if necessary: leave subpages_mapcount 0, don't bother with COMPOUND_MAPPED in its case, just carry on checking compound_mapcount too in folio_mapped(), page_mapped().
Evidence is that this way goes slightly faster than the previous implementation in all cases (pmds after ptes now taking around 103ms); and relieves us of worrying about contention on the bit_spin_lock.
---
v2: head_subpages_mapcount() apply the SUBPAGES_MAPPED mask, per Kirill
(which consequently modifies mm/page_alloc.c instead of mm/debug.c) reverse order of reads in folio_large_is_mapped(), per Kirill
Documentation/mm/transhuge.rst | 7 +- include/linux/mm.h | 19 +++++- include/linux/rmap.h | 13 ++-- mm/page_alloc.c | 2 +- mm/rmap.c | 121 +++++++-------------------------- 5 files changed, 51 insertions(+), 111 deletions(-)
Documentation/mm/transhuge.rst +3 -4
@@ -118,15 +118,14 @@ pages: succeeds on tail pages. - map/unmap of PMD entry for the whole compound page increment/decrement - ->compound_mapcount, stored in the first tail page of the compound page. + ->compound_mapcount, stored in the first tail page of the compound page; + and also increment/decrement ->subpages_mapcount (also in the first tail) + by COMPOUND_MAPPED when compound_mapcount goes from -1 to 0 or 0 to -1. - map/unmap of sub-pages with PTE entry increment/decrement ->_mapcount on relevant sub-page of the compound page, and also increment/decrement ->subpages_mapcount, stored in first tail page of the compound page, when _mapcount goes from -1 to 0 or 0 to -1: counting sub-pages mapped by PTE. - In order to have race-free accounting of sub-pages mapped, changes to - sub-page ->_mapcount, ->subpages_mapcount and ->compound_mapcount are - are all locked by bit_spin_lock of PG_locked in the first tail ->flags. split_huge_page internally has to distribute the refcounts in the head page to the tail pages before clearing all PG_head/tail bits from the page
include/linux/mm.h +16 -3
@@ -827,13 +827,22 @@ static inline int head_compound_mapcount(struct page *head)return atomic_read (compound_mapcount_ptr (head)) +1 ; } +/* +* If a 16GB hugetlb page were mapped by PTEs of all of its 4kB sub-pages, +* its subpages_mapcount would be 0x400000: choose the COMPOUND_MAPPED bit +* above that range, instead of 2*(PMD_SIZE/PAGE_SIZE). Hugetlb currently +* leaves subpages_mapcount at 0, but avoid surprise if it participates later. +*/ +#define COMPOUND_MAPPED 0x800000 +#define SUBPAGES_MAPPED (COMPOUND_MAPPED - 1) +/* * Number of sub-pages mapped by PTE, does not include compound mapcount. * Must be called only on head of compound page. */ static inline int head_subpages_mapcount (struct page *head) { -return atomic_read (subpages_mapcount_ptr (head)); +return atomic_read (subpages_mapcount_ptr (head)) &SUBPAGES_MAPPED ; }/*
@@ -893,8 +902,12 @@ static inline int total_mapcount(struct page *page)static inline bool folio_large_is_mapped (struct folio *folio) { -return atomic_read (folio_mapcount_ptr (folio)) + -atomic_read (folio_subpages_mapcount_ptr (folio)) >=0 ; +/* +* Reading folio_mapcount_ptr() below could be omitted if hugetlb +* participated in incrementing subpages_mapcount when compound mapped. +*/ +return atomic_read (folio_subpages_mapcount_ptr (folio)) >0 || +atomic_read (folio_mapcount_ptr (folio)) >=0 ; }/**
include/linux/rmap.h +6 -7
@@ -204,15 +204,14 @@ void hugepage_add_anon_rmap(struct page *, struct vm_area_struct *,void hugepage_add_new_anon_rmap (struct page *,struct vm_area_struct *,unsigned long address); -void page_dup_compound_rmap (struct page *page); +static inline void __page_dup_rmap (struct page *page,bool compound) +{ +atomic_inc (compound ?compound_mapcount_ptr (page) : &page->_mapcount); +}static inline void page_dup_file_rmap (struct page *page,bool compound) { -/* Is page being mapped by PTE? */ -if (likely (!compound)) -atomic_inc (&page->_mapcount); -else -page_dup_compound_rmap (page); +__page_dup_rmap (page, compound); }/**
@@ -261,7 +260,7 @@ static inline int page_try_dup_anon_rmap(struct page *page, bool compound,* the page R/O into both processes. */ dup: -page_dup_file_rmap (page, compound); +__page_dup_rmap (page, compound);return 0 ; }
mm/page_alloc.c +1 -1
@@ -1330,7 +1330,7 @@ static int free_tail_pages_check(struct page *head_page, struct page *page)bad_page (page,"nonzero compound_mapcount" ); goto out; } -if (unlikely (head_subpages_mapcount (head_page))) { +if (unlikely (atomic_read (subpages_mapcount_ptr (head_page)))) {bad_page (page,"nonzero subpages_mapcount" ); goto out; }
mm/rmap.c +25 -96
196 lines not on this page · raw message
Signature · 1 line
2.35.3
PATCH v2 3/3 mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
In reply to Hugh DickinsIt's hard to add a page_add_anon_rmap() into __split_huge_pmd_locked()'s HPAGE_PMD_NR set_pte_at() loop, without wincing at the "freeze" case's HPAGE_PMD_NR page_remove_rmap() loop below it.
It's just a mistake to add rmaps in the "freeze" (insert migration entries prior to splitting huge page) case: the pmd_migration case already avoids doing that, so just follow its lead. page_add_ref() versus put_page() likewise. But why is one more put_page() needed in the "freeze" case? Because it's removing the pmd rmap, already removed when pmd_migration (and freeze and pmd_migration are mutually exclusive cases).
---
v2: same as v1, plus Ack from Kirill
mm/huge_memory.c | 15 +++++---------- 1 file changed, 5 insertions(+), 10 deletions(-)
mm/huge_memory.c +5 -10
@@ -2135,7 +2135,6 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, uffd_wp =pmd_uffd_wp (old_pmd);VM_BUG_ON_PAGE (!page_count (page), page); -page_ref_add (page,HPAGE_PMD_NR -1 );/* * Without "freeze", we'll simply split the PMD, propagating the
@@ -2155,6 +2154,8 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, anon_exclusive =PageAnon (page) &&PageAnonExclusive (page);if (freeze && anon_exclusive &&page_try_share_anon_rmap (page)) freeze = false; +if (!freeze) +page_ref_add (page,HPAGE_PMD_NR -1 ); }/*
@@ -2210,27 +2211,21 @@ static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, entry =pte_mksoft_dirty (entry);if (uffd_wp) entry =pte_mkuffd_wp (entry); +page_add_anon_rmap (page + i, vma, addr, false); } pte =pte_offset_map (&_pmd, addr);BUG_ON (!pte_none (*pte));set_pte_at (mm, addr, pte, entry); -if (!pmd_migration) -page_add_anon_rmap (page + i, vma, addr, false);pte_unmap (pte); }if (!pmd_migration)page_remove_rmap (page, vma, true); +if (freeze) +put_page (page);smp_wmb ();/* make pte visible before pmd */ pmd_populate (mm, pmd, pgtable); - -if (freeze) { -for (i =0 ; i <HPAGE_PMD_NR ; i++) { -page_remove_rmap (page + i, vma, false); -put_page (page + i); - } - } } void __split_huge_pmd(struct vm_area_struct *vma, pmd_t *pmd,
Signature · 1 line
2.35.3
Re: [PATCH v2 3/3] mm,thp,rmap: clean up the end of __split_huge_pmd_locked()
Quoted 3 lines · Hugh Dickins
It's hard to add a
page_add_anon_rmap()into __split_huge_pmd_locked()'sHPAGE_PMD_NRset_pte_at()loop, without wincing at the "freeze" case'sHPAGE_PMD_NRpage_remove_rmap()loop below it.
No problem here, but I did later learn something worth sharing.
Comparing before and after vmstats for the series, I was worried to find the thp_deferred_split_page count consistently much lower afterwards (10%? 1%?), and thought maybe the COMPOUND_MAPPED patch had messed up the accounting for when to call deferred_split_huge_page().
But no: that's as before. We can debate sometime whether it could do a better job - the vast majority of calls to deferred_split_huge_page() are just repeats - but that's a different story, one I'm not keen to get into at the moment.
mm/huge_memory.c static void __split_huge_pmd_locked(struct vm_area_struct *vma, pmd_t *pmd, · line 2233
Quoted 6 lines
mm/huge_memory.c +0
-6-if (freeze) { -for (i =0 ; i <HPAGE_PMD_NR ; i++) { -page_remove_rmap (page + i, vma, false); -put_page (page + i); - } - }
The reason for the lower thp_deferred_split_page (at least in the kind of testing I was doing) was a very good thing: those page_remove_rmap() calls from __split_huge_pmd_locked() had very often been adding the page to the deferred split queue, precisely while it was already being split.
The list management is such that there was no corruption, and splitting calls from the split queue itself did not reach the point of bumping up the thp_deferred_split_page count; but off-queue splits would add the page before deleting it again, adding lots of noise to the count, and unnecessary contention on the queue lock I presume.
Hugh