* [PATCH] mm, page_alloc: print reserved_highatomic info
@ 2019-11-13 8:59 lijiazi
0 siblings, 0 replies; only message in thread
From: lijiazi @ 2019-11-13 8:59 UTC (permalink / raw)
To: Andrew Morton; +Cc: lijiazi, linux-mm
Pintf nr_reserved_highatomic in show_free_areas, because when
alloc_harder is false, this value will be subtracted from the
free_pages in __zone_watermark_ok. Print this value can help
analyze mem alloc fail issue.
Signed-off-by: lijiazi <lijiazi@xiaomi.com>
---
mm/page_alloc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index f391c0c..8b78a93 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -5354,6 +5354,7 @@ void show_free_areas(unsigned int filter, nodemask_t *nodemask)
" min:%lukB"
" low:%lukB"
" high:%lukB"
+ " reserved_highatomic:%luKB"
" active_anon:%lukB"
" inactive_anon:%lukB"
" active_file:%lukB"
@@ -5375,6 +5376,7 @@ void show_free_areas(unsigned int filter, nodemask_t *nodemask)
K(min_wmark_pages(zone)),
K(low_wmark_pages(zone)),
K(high_wmark_pages(zone)),
+ K(zone->nr_reserved_highatomic),
K(zone_page_state(zone, NR_ZONE_ACTIVE_ANON)),
K(zone_page_state(zone, NR_ZONE_INACTIVE_ANON)),
K(zone_page_state(zone, NR_ZONE_ACTIVE_FILE)),
--
2.7.4
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-11-13 9:00 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-13 8:59 [PATCH] mm, page_alloc: print reserved_highatomic info lijiazi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox