From: Anshuman Khandual <anshuman.khandual@arm.com>
To: gaoxu <gaoxu2@honor.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Rapoport <rppt@kernel.org>,
"surenb@google.com" <surenb@google.com>,
Yu Zhao <yuzhao@google.com>, Barry Song <21cnbao@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
yipengxiang <yipengxiang@honor.com>
Subject: Re: [PATCH] mm: add nr_free_highatomic in show_free_areas
Date: Tue, 15 Apr 2025 12:10:07 +0530 [thread overview]
Message-ID: <a7c8f6fe-19c9-4546-900a-3d164ec37a94@arm.com> (raw)
In-Reply-To: <d92eeff74f7a4578a14ac777cfe3603a@honor.com>
On 4/12/25 14:57, gaoxu wrote:
> The commit c928807f6f6b6("mm/page_alloc: keep track of free highatomic")
> adds a new variable nr_free_highatomic, which is useful for analyzing low
> mem issues. add nr_free_highatomic in show_free_areas.
>
> Signed-off-by: gao xu <gaoxu2@honor.com>
> ---
> mm/show_mem.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/show_mem.c b/mm/show_mem.c
> index ad373b4b6..03e8d968f 100644
> --- a/mm/show_mem.c
> +++ b/mm/show_mem.c
> @@ -305,6 +305,7 @@ static void show_free_areas(unsigned int filter, nodemask_t *nodemask, int max_z
> " low:%lukB"
> " high:%lukB"
> " reserved_highatomic:%luKB"
> + " free_highatomic:%luKB"
> " active_anon:%lukB"
> " inactive_anon:%lukB"
> " active_file:%lukB"
> @@ -326,6 +327,7 @@ static void show_free_areas(unsigned int filter, nodemask_t *nodemask, int max_z
> K(low_wmark_pages(zone)),
> K(high_wmark_pages(zone)),
> K(zone->nr_reserved_highatomic),
> + K(zone->nr_free_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)),
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
prev parent reply other threads:[~2025-04-15 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 9:27 gaoxu
2025-04-13 20:47 ` David Hildenbrand
2025-04-13 21:52 ` Barry Song
2025-04-15 6:40 ` Anshuman Khandual [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a7c8f6fe-19c9-4546-900a-3d164ec37a94@arm.com \
--to=anshuman.khandual@arm.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gaoxu2@honor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=yipengxiang@honor.com \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox