mm/highmem: don't track highmem pages manually
Subsystems (3)
cover mm/highmem: don't track highmem pages manually
Let's remove highmem special-casing from adjust_managed_page_count(), to result in less confusion why memblock manually adjusts totalram_pages, and __free_pages_core() only adjusts the zone's managed pages -- what about the highmem pages that adjust_managed_page_count() updates?
Now, we only maintain totalram_pages and a zone's managed pages independent of highmem support. We can derive the number of highmem pages simply by looking at the relevant zone's managed pages. I don't think there is any particular fast path that needs a maximum-efficient totalhigh_pages() implementation.
Note that highmem memory is currently initialized using free_highmem_page()->free_reserved_page(), not __free_pages_core(). In the future we might want to also use __free_pages_core() to initialize highmem memory, to make that less special, and consider moving totalram_pages updates into __free_pages_core() [1], so we can just use adjust_managed_page_count() in there as well.
Booting a simple kernel in QEMU reveals no highmem accounting change:
Before:
Memory: 3095448K/3145208K available (14802K kernel code, 2073K rwdata, 5000K rodata, 740K init, 556K bss, 49760K reserved, 0K cma-reserved, 2244488K highmem)
After:
Memory: 3095276K/3145208K available (14802K kernel code, 2073K rwdata, 5000K rodata, 740K init, 556K bss, 49932K reserved, 0K cma-reserved, 2244488K highmem)
[1] https://lkml.kernel.org/r/[email protected]
David Hildenbrand (2):
mm/highmem: reimplement totalhigh_pages() by walking zones mm/highmem: make nr_free_highpages() return "unsigned long"
include/linux/highmem-internal.h | 17 ++++++----------- include/linux/highmem.h | 2 +- mm/highmem.c | 20 +++++++++++++++----- mm/page_alloc.c | 4 ---- 4 files changed, 22 insertions(+), 21 deletions(-)
base-commit: 19b8422c5bd56fb5e7085995801c6543a98bda1f
Signature · 1 line
2.45.1
PATCH 1/2 mm/highmem: reimplement totalhigh_pages() by walking zones
Can we get rid of the highmem ifdef in adjust_managed_page_count()? Likely yes: we don't have that many totalhigh_pages() users, and they all don't seem to be very performance critical.
So let's implement totalhigh_pages() like nr_free_highpages(), collecting information from all zones. This is now similar to what we do in si_meminfo_node() to collect the per-node highmem page count.
In the common case (single node, 3-4 zones), we really shouldn't care. We could optimize a bit further (only walk ZONE_HIGHMEM and ZONE_MOVABLE if required), but there doesn't seem a real need for that.
--- include/linux/highmem-internal.h | 9 ++------- mm/highmem.c | 16 +++++++++++++--- mm/page_alloc.c | 4 ---- 3 files changed, 15 insertions(+), 14 deletions(-)
include/linux/highmem-internal.h +2 -7
@@ -132,7 +132,7 @@ static inline void __kunmap_atomic(const void *addr) }unsigned int __nr_free_highpages (void ); -extern atomic_long_t _totalhigh_pages; +unsigned long __totalhigh_pages (void );static inline unsigned int nr_free_highpages (void ) {
@@ -141,12 +141,7 @@ static inline unsigned int nr_free_highpages(void)static inline unsigned long totalhigh_pages (void ) { -return (unsigned long )atomic_long_read (&_totalhigh_pages); -} - -static inline void totalhigh_pages_add (long count) -{ -atomic_long_add (count, &_totalhigh_pages); +return __totalhigh_pages (); }static inline bool is_kmap_addr (const void *x)
mm/highmem.c +13 -3
@@ -111,9 +111,6 @@ static inline wait_queue_head_t *get_pkmap_wait_queue_head(unsigned int color) }#endif -atomic_long_t _totalhigh_pages__read_mostly ; -EXPORT_SYMBOL (_totalhigh_pages); -unsigned int __nr_free_highpages (void ) {struct zone *zone;
@@ -127,6 +124,19 @@ unsigned int __nr_free_highpages(void)return pages; } +unsigned long __totalhigh_pages (void ) +{ +unsigned long pages =0 ; +struct zone *zone; + +for_each_populated_zone (zone) { +if (is_highmem (zone)) + pages +=zone_managed_pages (zone); + } + +return pages; +} +static int pkmap_count[LAST_PKMAP ];static __cacheline_aligned_in_smp DEFINE_SPINLOCK (kmap_lock );
mm/page_alloc.c +0 -4
@@ -5794,10 +5794,6 @@ void adjust_managed_page_count(struct page *page, long count) {atomic_long_add (count, &page_zone (page)->managed_pages);totalram_pages_add (count); -#ifdef CONFIG_HIGHMEM -if (PageHighMem (page)) -totalhigh_pages_add (count); -#endif }EXPORT_SYMBOL (adjust_managed_page_count);
Signature · 1 line
2.45.1
Re: [PATCH v1 1/2] mm/highmem: reimplement totalhigh_pages() by walking zones
Quoted 67 lines · David Hildenbrand
Can we get rid of the highmem ifdef in
adjust_managed_page_count()? Likely yes: we don't have that manytotalhigh_pages()users, and they all don't seem to be very performance critical.So let's implement
totalhigh_pages()likenr_free_highpages(), collecting information from all zones. This is now similar to what we do insi_meminfo_node()to collect the per-node highmem page count.In the common case (single node, 3-4 zones), we really shouldn't care. We could optimize a bit further (only walk
ZONE_HIGHMEMandZONE_MOVABLEif required), but there doesn't seem a real need for that.Signed-off-by David Hildenbrand <[email protected]>--- include/linux/highmem-internal.h | 9 ++------- mm/highmem.c | 16 +++++++++++++--- mm/page_alloc.c | 4 ---- 3 files changed, 15 insertions(+), 14 deletions(-)include/linux/highmem-internal.h +2
-7@@ -132,7 +132,7 @@ static inline void __kunmap_atomic(const void *addr) }unsigned int __nr_free_highpages (void ); -extern atomic_long_t _totalhigh_pages; +unsigned long __totalhigh_pages (void );static inline unsigned int nr_free_highpages (void ) {@@ -141,12 +141,7 @@ static inline unsigned int nr_free_highpages(void)static inline unsigned long totalhigh_pages (void ) { -return (unsigned long )atomic_long_read (&_totalhigh_pages); -} - -static inline void totalhigh_pages_add (long count) -{ -atomic_long_add (count, &_totalhigh_pages); +return __totalhigh_pages (); }static inline bool is_kmap_addr (const void *x)mm/highmem.c +3
-3@@ -111,9 +111,6 @@ static inline wait_queue_head_t *get_pkmap_wait_queue_head(unsigned int color) }#endif -atomic_long_t _totalhigh_pages__read_mostly ; -EXPORT_SYMBOL (_totalhigh_pages); -unsigned int __nr_free_highpages (void ) {struct zone *zone;@@ -127,6 +124,19 @@ unsigned int __nr_free_highpages(void)return pages; } +unsigned long __totalhigh_pages (void ) +{ +unsigned long pages =0 ;
mm/highmem.c unsigned int __nr_free_highpages(void) · line 139
Quoted 10 lines
mm/highmem.c +10
-0+struct zone *zone; + +for_each_populated_zone (zone) { +if (is_highmem (zone)) + pages +=zone_managed_pages (zone); + } + +return pages; +} +
Another (later than usual, but better late than never) build bot complaint:
mm/highmem.c +1 -0
@@ -136,6 +136,7 @@ unsigned long __totalhigh_pages(void)return pages; } +EXPORT_SYMBOL (__totalhigh_pages);static int pkmap_count[LAST_PKMAP ];static __cacheline_aligned_in_smp DEFINE_SPINLOCK (kmap_lock );
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH v1 1/2] mm/highmem: reimplement totalhigh_pages() by walking zones
In reply to David HildenbrandQuoted 8 lines · David Hildenbrand
Can we get rid of the highmem ifdef in
adjust_managed_page_count()? Likely yes: we don't have that manytotalhigh_pages()users, and they all don't seem to be very performance critical.So let's implement
totalhigh_pages()likenr_free_highpages(), collecting information from all zones. This is now similar to what we do insi_meminfo_node()to collect the per-node highmem page count.
Quoted 5 lines
In the common case (single node, 3-4 zones), we really shouldn't care. We could optimize a bit further (only walk
ZONE_HIGHMEMandZONE_MOVABLEif required), but there doesn't seem a real need for that.Signed-off-by David Hildenbrand <[email protected]>
Quoted 84 lines
---
include/linux/highmem-internal.h | 9 ++------- mm/highmem.c | 16 +++++++++++++--- mm/page_alloc.c | 4 ---- 3 files changed, 15 insertions(+), 14 deletions(-)include/linux/highmem-internal.h +2
-7@@ -132,7 +132,7 @@ static inline void __kunmap_atomic(const void *addr) }unsigned int __nr_free_highpages (void ); -extern atomic_long_t _totalhigh_pages; +unsigned long __totalhigh_pages (void );static inline unsigned int nr_free_highpages (void ) {@@ -141,12 +141,7 @@ static inline unsigned int nr_free_highpages(void)static inline unsigned long totalhigh_pages (void ) { -return (unsigned long )atomic_long_read (&_totalhigh_pages); -} - -static inline void totalhigh_pages_add (long count) -{ -atomic_long_add (count, &_totalhigh_pages); +return __totalhigh_pages (); }static inline bool is_kmap_addr (const void *x)mm/highmem.c +13
-3@@ -111,9 +111,6 @@ static inline wait_queue_head_t *get_pkmap_wait_queue_head(unsigned int color) }#endif -atomic_long_t _totalhigh_pages__read_mostly ; -EXPORT_SYMBOL (_totalhigh_pages); -unsigned int __nr_free_highpages (void ) {struct zone *zone;@@ -127,6 +124,19 @@ unsigned int __nr_free_highpages(void)return pages; } +unsigned long __totalhigh_pages (void ) +{ +unsigned long pages =0 ; +struct zone *zone; + +for_each_populated_zone (zone) { +if (is_highmem (zone)) + pages +=zone_managed_pages (zone); + } + +return pages; +} +static int pkmap_count[LAST_PKMAP ];static __cacheline_aligned_in_smp DEFINE_SPINLOCK (kmap_lock );mm/page_alloc.c +0
-4@@ -5794,10 +5794,6 @@ void adjust_managed_page_count(struct page *page, long count) {atomic_long_add (count, &page_zone (page)->managed_pages);totalram_pages_add (count); -#ifdef CONFIG_HIGHMEM -if (PageHighMem (page)) -totalhigh_pages_add (count); -#endif }EXPORT_SYMBOL (adjust_managed_page_count);Signature · 1 line
2.45.1
Signature · 2 lines
Wei Yang Help you, Help me
Re: [PATCH v1 1/2] mm/highmem: reimplement totalhigh_pages() by walking zones
In reply to David HildenbrandQuoted 8 lines · David Hildenbrand
Can we get rid of the highmem ifdef in
adjust_managed_page_count()? Likely yes: we don't have that manytotalhigh_pages()users, and they all don't seem to be very performance critical.So let's implement
totalhigh_pages()likenr_free_highpages(), collecting information from all zones. This is now similar to what we do insi_meminfo_node()to collect the per-node highmem page count.
Quoted 5 lines
In the common case (single node, 3-4 zones), we really shouldn't care. We could optimize a bit further (only walk
ZONE_HIGHMEMandZONE_MOVABLEif required), but there doesn't seem a real need for that.Signed-off-by David Hildenbrand <[email protected]>
Signature · 2 lines
Oscar Salvador SUSE Labs
PATCH 2/2 mm/highmem: make nr_free_highpages() return "unsigned long"
In reply to David HildenbrandIt looks rather weird that totalhigh_pages() returns an "unsigned long" but nr_free_highpages() returns an "unsigned int".
Let's return an "unsigned long" from nr_free_highpages() to be consistent.
While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM totalhigh_pages() implementation, to make these look alike as well.
--- include/linux/highmem-internal.h | 8 ++++---- include/linux/highmem.h | 2 +- mm/highmem.c | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-)
include/linux/highmem-internal.h +4 -4
@@ -131,10 +131,10 @@ static inline void __kunmap_atomic(const void *addr)preempt_enable (); } -unsigned int __nr_free_highpages (void ); +unsigned long __nr_free_highpages (void );unsigned long __totalhigh_pages (void ); -static inline unsigned int nr_free_highpages (void ) +static inline unsigned long nr_free_highpages (void ) {return __nr_free_highpages (); }
@@ -234,8 +234,8 @@ static inline void __kunmap_atomic(const void *addr)preempt_enable (); } -static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }static inline bool is_kmap_addr (const void *x) {
include/linux/highmem.h +1 -1
@@ -179,7 +179,7 @@ static inline void *kmap_local_folio(struct folio *folio, size_t offset);static inline void *kmap_atomic (struct page *page);/* Highmem related interfaces for management code */ -static inline unsigned int nr_free_highpages (void ); +static inline unsigned long nr_free_highpages (void );static inline unsigned long totalhigh_pages (void );#ifndef ARCH_HAS_FLUSH_ANON_PAGE
mm/highmem.c +2 -2
@@ -111,10 +111,10 @@ static inline wait_queue_head_t *get_pkmap_wait_queue_head(unsigned int color) }#endif -unsigned int __nr_free_highpages (void ) +unsigned long __nr_free_highpages (void ) { +unsigned long pages =0 ;struct zone *zone; -unsigned int pages =0 ;for_each_populated_zone (zone) {if (is_highmem (zone))
Signature · 1 line
2.45.1
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 8 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.
I am not sure why not use 0UL for both?
Quoted 68 lines
Signed-off-by David Hildenbrand <[email protected]>---
include/linux/highmem-internal.h | 8 ++++---- include/linux/highmem.h | 2 +- mm/highmem.c | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-)include/linux/highmem-internal.h +4
-4@@ -131,10 +131,10 @@ static inline void __kunmap_atomic(const void *addr)preempt_enable (); } -unsigned int __nr_free_highpages (void ); +unsigned long __nr_free_highpages (void );unsigned long __totalhigh_pages (void ); -static inline unsigned int nr_free_highpages (void ) +static inline unsigned long nr_free_highpages (void ) {return __nr_free_highpages (); }@@ -234,8 +234,8 @@ static inline void __kunmap_atomic(const void *addr)preempt_enable (); } -static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }static inline bool is_kmap_addr (const void *x) {include/linux/highmem.h +1
-1@@ -179,7 +179,7 @@ static inline void *kmap_local_folio(struct folio *folio, size_t offset);static inline void *kmap_atomic (struct page *page);/* Highmem related interfaces for management code */ -static inline unsigned int nr_free_highpages (void ); +static inline unsigned long nr_free_highpages (void );static inline unsigned long totalhigh_pages (void );#ifndef ARCH_HAS_FLUSH_ANON_PAGE mm/highmem.c +2
-2@@ -111,10 +111,10 @@ static inline wait_queue_head_t *get_pkmap_wait_queue_head(unsigned int color) }#endif -unsigned int __nr_free_highpages (void ) +unsigned long __nr_free_highpages (void ) { +unsigned long pages =0 ;struct zone *zone; -unsigned int pages =0 ;for_each_populated_zone (zone) {if (is_highmem (zone))Signature · 1 line
2.45.1
Signature · 2 lines
Wei Yang Help you, Help me
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 11 lines · Wei Yang
Quoted 8 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.I am not sure why not use 0UL for both?
See my reply to Oscar, thanks for the review!
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
In reply to David HildenbrandQuoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }
Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
Other than that
Signature · 2 lines
Oscar Salvador SUSE Labs
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>
Quoted 8 lines
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in include/linux we now have:
t14s: ~/git/linux/include/linux $ git grep "return 0UL;"skbuff.h: return 0UL;
uaccess.h:static inline unsigned long user_access_save(void) { return 0UL; }
t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;
uaccess.h:static inline unsigned long user_access_save(void) { return 0UL; }
... compared to a long list if "unsigned long" functions that simply "return 0;"
So I prefer to just drop it.
Thanks!
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 38 lines · David Hildenbrand
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>Quoted 8 lines
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in
include/linuxwe now have:t14s: ~/git/linux/include/linux $ git grep "return 0UL;"
skbuff.h: return 0UL;
uaccess.h:static inline unsigned longuser_access_save(void){ return 0UL; }t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;
Quoted 5 lines
uaccess.h:static inline unsigned long
user_access_save(void){ return 0UL; }... compared to a long list if "unsigned long" functions that simply "return 0;"
Seems this is the current status.
Then my question is do we have a guide line for this? Or 0 is the special case? Sounds positive value has no sign extension problem. If we need to return 1, we suppose to use 1 or 1UL? I found myself confused.
I grepped "return 1" and do find some cases without UL:
backing-dev.h: wb_stat_error() return 1 for unsigned long. pgtable.h: pte_batch_hint() return 1 for unsigned int.
So the guide line is for positive value, it is not necessary to use UL?
Quoted 9 lines
So I prefer to just drop it.
Thanks!
Signature · 3 lines
Cheers, David / dhildenb
Signature · 2 lines
Wei Yang Help you, Help me
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 51 lines · Wei Yang
Quoted 38 lines · David Hildenbrand
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>Quoted 8 lines
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in
include/linuxwe now have:t14s: ~/git/linux/include/linux $ git grep "return 0UL;"
skbuff.h: return 0UL;
uaccess.h:static inline unsigned longuser_access_save(void){ return 0UL; }t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;Quoted 5 lines
uaccess.h:static inline unsigned long
user_access_save(void){ return 0UL; }... compared to a long list if "unsigned long" functions that simply "return 0;"
Seems this is the current status.
Then my question is do we have a guide line for this? Or 0 is the special case? Sounds positive value has no sign extension problem. If we need to return 1, we suppose to use 1 or 1UL? I found myself confused.
Quoted 6 lines
I grepped "return 1" and do find some cases without UL:
backing-dev.h:wb_stat_error()return 1 for unsigned long.pgtable.h:pte_batch_hint()return 1 for unsigned int.So the guide line is for positive value, it is not necessary to use UL?
I think when returning simple values (0/1/-1), we really don't need these suffices at all. The standard says "The type of an integer constant is the first of the corresponding list in which its value can be represented.". I thought it would always use an "int", but that is not the case.
So, if we use "-1", the compiler will use an "int", and sign extension to "unsigned" long will do the right thing.
Simple test:
-1 results in: 0xffffffffffffffff
-1U results in: 0xffffffff
-1UL results in: 0xffffffffffffffff 0xffffffff results in: 0xffffffff 0xffffffffU results in: 0xffffffff 0xffffffffUL results in: 0xffffffff ~0xffffffff results in: 0x0
~0xffffffffU results in: 0x0
~0xffffffffUL results in: 0xffffffff00000000 0xffffffffffffffff results in: 0xffffffffffffffff 0xffffffffffffffffU results in: 0xffffffffffffffff 0xffffffffffffffffUL results in: 0xffffffffffffffff
I thought that "0xffffffff" could be a problem (sign-extending to 0xffffffffffffffff), but that does not seem to be the case -- likely using "unsigned int" as type. Also, I'm surprised that 0xffffffffffffffffU works as expected, I would have thought the "U" would make the compiler complain about the value not fitting into an unsigned int.
When only returning values, the compiler usually does the right thing. Only when performing operations on the constant (see ~ example above), we might have to use the suffixes, depending on the intended outcome.
Signature · 3 lines
Cheers, David / dhildenb
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 69 lines · David Hildenbrand
Quoted 51 lines · Wei Yang
Quoted 38 lines · David Hildenbrand
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>Quoted 8 lines
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in
include/linuxwe now have:t14s: ~/git/linux/include/linux $ git grep "return 0UL;"
skbuff.h: return 0UL;
uaccess.h:static inline unsigned longuser_access_save(void){ return 0UL; }t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;Quoted 5 lines
uaccess.h:static inline unsigned long
user_access_save(void){ return 0UL; }... compared to a long list if "unsigned long" functions that simply "return 0;"
Seems this is the current status.
Then my question is do we have a guide line for this? Or 0 is the special case? Sounds positive value has no sign extension problem. If we need to return 1, we suppose to use 1 or 1UL? I found myself confused.
Quoted 6 lines
I grepped "return 1" and do find some cases without UL:
backing-dev.h:wb_stat_error()return 1 for unsigned long.pgtable.h:pte_batch_hint()return 1 for unsigned int.So the guide line is for positive value, it is not necessary to use UL?
I think when returning simple values (0/1/-1), we really don't need these suffices at all. The standard says "The type of an integer constant is the first of the corresponding list in which its value can be represented.". I thought it would always use an "int", but that is not the case.
So, if we use "-1", the compiler will use an "int", and sign extension to "unsigned" long will do the right thing.
Simple test:
Quoted 11 lines
-1 results in:
0xffffffffffffffff
-1U results in:0xffffffff
-1UL results in:0xffffffffffffffff0xffffffffresults in:0xffffffff0xffffffffUresults in:0xffffffff0xffffffffULresults in:0xffffffff~0xffffffff results in:0x0
~0xffffffffU results in:0x0
~0xffffffffUL results in:0xffffffff000000000xffffffffffffffffresults in:0xffffffffffffffff0xffffffffffffffffUresults in:0xffffffffffffffff
I expect this to be 0xffffffff. Why this extend it to a UL?
Quoted 10 lines
0xffffffffffffffffULresults in:0xffffffffffffffffI thought that "
0xffffffff" could be a problem (sign-extending to0xffffffffffffffff), but that does not seem to be the case -- likely using "unsigned int" as type. Also, I'm surprised that0xffffffffffffffffUworks as expected, I would have thought the "U" would make the compiler complain about the value not fitting into an unsigned int.
Quoted 4 lines
When only returning values, the compiler usually does the right thing. Only when performing operations on the constant (see ~ example above), we might have to use the suffixes, depending on the intended outcome.
Looks the guide line is
* no need to put suffix on return value
* add suffix when performing operations, like ~, <<
Quoted 4 lines
Signature · 3 lines
Cheers, David / dhildenb
Signature · 2 lines
Wei Yang Help you, Help me
Re: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 82 lines · Wei Yang
Quoted 69 lines · David Hildenbrand
Quoted 51 lines · Wei Yang
Quoted 38 lines · David Hildenbrand
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>Quoted 8 lines
...
include/linux/highmem-internal.h static inline void __kunmap_atomic(const void *addr) · line 238
Quoted 4 lines
include/linux/highmem-internal.h +2
-2-static inline unsigned int nr_free_highpages (void ) {return 0 ; } -static inline unsigned long totalhigh_pages (void ) {return 0UL ; } +static inline unsigned long nr_free_highpages (void ) {return 0 ; } +static inline unsigned long totalhigh_pages (void ) {return 0 ; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in
include/linuxwe now have:t14s: ~/git/linux/include/linux $ git grep "return 0UL;"
skbuff.h: return 0UL;
uaccess.h:static inline unsigned longuser_access_save(void){ return 0UL; }t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;Quoted 5 lines
uaccess.h:static inline unsigned long
user_access_save(void){ return 0UL; }... compared to a long list if "unsigned long" functions that simply "return 0;"
Seems this is the current status.
Then my question is do we have a guide line for this? Or 0 is the special case? Sounds positive value has no sign extension problem. If we need to return 1, we suppose to use 1 or 1UL? I found myself confused.
Quoted 6 lines
I grepped "return 1" and do find some cases without UL:
backing-dev.h:wb_stat_error()return 1 for unsigned long.pgtable.h:pte_batch_hint()return 1 for unsigned int.So the guide line is for positive value, it is not necessary to use UL?
I think when returning simple values (0/1/-1), we really don't need these suffices at all. The standard says "The type of an integer constant is the first of the corresponding list in which its value can be represented.". I thought it would always use an "int", but that is not the case.
So, if we use "-1", the compiler will use an "int", and sign extension to "unsigned" long will do the right thing.
Simple test:
Quoted 11 lines
-1 results in:
0xffffffffffffffff
-1U results in:0xffffffff
-1UL results in:0xffffffffffffffff0xffffffffresults in:0xffffffff0xffffffffUresults in:0xffffffff0xffffffffULresults in:0xffffffff~0xffffffff results in:0x0
~0xffffffffU results in:0x0
~0xffffffffUL results in:0xffffffff000000000xffffffffffffffffresults in:0xffffffffffffffff0xffffffffffffffffUresults in:0xffffffffffffffff
Quoted 1 line
I expect this to be
0xffffffff. Why this extend it to a UL?
Apparently, the "U" only restricts the set of types to "unsigned ones".
https://en.cppreference.com/w/cpp/language/integer_literal
So the compiler will use the first "unsigned" type that can hold that value.
Signature · 3 lines
Cheers, David / dhildenb
Wei Yang
Reviewed-byRe: [PATCH v1 2/2] mm/highmem: make nr_free_highpages() return "unsigned long"
Quoted 83 lines · David Hildenbrand
Quoted 82 lines · Wei Yang
Quoted 80 lines · David Hildenbrand
Quoted 51 lines · Wei Yang
Quoted 38 lines · David Hildenbrand
Quoted 11 lines · Oscar Salvador
Quoted 10 lines · David Hildenbrand
It looks rather weird that
totalhigh_pages()returns an "unsigned long" butnr_free_highpages()returns an "unsigned int".Let's return an "unsigned long" from
nr_free_highpages()to be consistent.While at it, use a plain "0" instead of a "0UL" in the !CONFIG_HIGHMEM
totalhigh_pages()implementation, to make these look alike as well.Signed-off-by David Hildenbrand <[email protected]>Quoted 8 lines
...
Review
Quoted 4 lines
(quoted diff) +2
-2-static inline unsigned int nr_free_highpages(void) { return 0; } -static inline unsigned long totalhigh_pages(void) { return 0UL; } +static inline unsigned long nr_free_highpages(void) { return 0; } +static inline unsigned long totalhigh_pages(void) { return 0; }Although I doubt it has any consequences, I would just leave them both with UL, so the return type is consistent with what we are returning.
These suffixes are only required when using constants that would not fit into the native (int) type, or converting from that native (int) type to something else automatically by the compiler would mess things up (for example, undesired sign extension). For 0 that is certainly impossible :)
That's also the reason why in
include/linuxwe now have:t14s: ~/git/linux/include/linux $ git grep "return 0UL;"
skbuff.h: return 0UL;
uaccess.h:static inline unsigned longuser_access_save(void){ return 0UL; }t14s: ~/git/linux/include/linux $ git grep "0UL;" bitmap.h: *dst = ~0UL; dax.h: return ~0UL; mtd/map.h: r.x[i] = ~0UL; netfilter.h: return ((ul1[0] ^ ul2[0]) | (ul1[1] ^ ul2[1])) == 0UL; skbuff.h: return 0UL;Quoted 5 lines
uaccess.h:static inline unsigned long
user_access_save(void){ return 0UL; }... compared to a long list if "unsigned long" functions that simply "return 0;"
Seems this is the current status.
Then my question is do we have a guide line for this? Or 0 is the special case? Sounds positive value has no sign extension problem. If we need to return 1, we suppose to use 1 or 1UL? I found myself confused.
Quoted 6 lines
I grepped "return 1" and do find some cases without UL:
backing-dev.h:wb_stat_error()return 1 for unsigned long.pgtable.h:pte_batch_hint()return 1 for unsigned int.So the guide line is for positive value, it is not necessary to use UL?
I think when returning simple values (0/1/-1), we really don't need these suffices at all. The standard says "The type of an integer constant is the first of the corresponding list in which its value can be represented.". I thought it would always use an "int", but that is not the case.
So, if we use "-1", the compiler will use an "int", and sign extension to "unsigned" long will do the right thing.
Simple test:
-1 results in:
0xffffffffffffffff
-1U results in:0xffffffff
-1UL results in:0xffffffffffffffff0xffffffffresults in:0xffffffff0xffffffffUresults in:0xffffffff0xffffffffULresults in:0xffffffff~0xffffffff results in:0x0
~0xffffffffU results in:0x0
~0xffffffffUL results in:0xffffffff000000000xffffffffffffffffresults in:0xffffffffffffffff0xffffffffffffffffUresults in:0xffffffffffffffff
Quoted 8 lines
Quoted 1 line
I expect this to be
0xffffffff. Why this extend it to a UL?Apparently, the "U" only restricts the set of types to "unsigned ones".
https://en.cppreference.com/w/cpp/language/integer_literal
So the compiler will use the first "unsigned" type that can hold that value.
Interesting, thanks for the reference.
Quoted 4 lines
Signature · 3 lines
Cheers, David / dhildenb
Signature · 2 lines
Wei Yang Help you, Help me
Quoted 6 lines · David Hildenbrand
Let's remove highmem special-casing from
adjust_managed_page_count(), to result in less confusion why memblock manually adjuststotalram_pages, and__free_pages_core()only adjusts the zone's managed pages -- what about the highmem pages thatadjust_managed_page_count()updates?
Thanks David
I have looked into this function and willing to get rid of it, but not found a good way.
Your change really look nice.
Quoted 44 lines
Now, we only maintain
totalram_pagesand a zone's managed pages independent of highmem support. We can derive the number of highmem pages simply by looking at the relevant zone's managed pages. I don't think there is any particular fast path that needs a maximum-efficienttotalhigh_pages()implementation.Note that highmem memory is currently initialized using free_highmem_page()->free_reserved_page(), not
__free_pages_core(). In the future we might want to also use__free_pages_core()to initialize highmem memory, to make that less special, and consider movingtotalram_pagesupdates into__free_pages_core()[1], so we can just useadjust_managed_page_count()in there as well.Booting a simple kernel in QEMU reveals no highmem accounting change:
Before:
Memory: 3095448K/3145208K available (14802K kernel code, 2073K rwdata, 5000K rodata, 740K init, 556K bss, 49760K reserved, 0K cma-reserved, 2244488K highmem)After:
Memory: 3095276K/3145208K available (14802K kernel code, 2073K rwdata, 5000K rodata, 740K init, 556K bss, 49932K reserved, 0K cma-reserved, 2244488K highmem)[1] https://lkml.kernel.org/r/[email protected]
Cc Andrew Morton <[email protected]>Cc Wei Yang <[email protected]>David Hildenbrand (2):
mm/highmem: reimplementtotalhigh_pages()by walking zones mm/highmem: makenr_free_highpages()return "unsigned long"include/linux/highmem-internal.h | 17 ++++++----------- include/linux/highmem.h | 2 +- mm/highmem.c | 20 +++++++++++++++----- mm/page_alloc.c | 4 ---- 4 files changed, 22 insertions(+), 21 deletions(-)base-commit:
19b8422c5bd56fb5e7085995801c6543a98bda1fSignature · 1 line
2.45.1
Signature · 2 lines
Wei Yang Help you, Help me