From: Martin Liu <liumartin@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-mm@kvack.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
minchan@kernel.org, Suren Baghdasaryan <surenb@google.com>
Subject: Re: [PATCH v2 0/3] Add tracepoints for lowmem reserves, watermarks and totalreserve_pages
Date: Wed, 12 Mar 2025 23:50:34 +0800 [thread overview]
Message-ID: <CAASV4h4_xgJPZOvh8k5snJc_ocvwPih+SvK9D8+_Fid2chcz6Q@mail.gmail.com> (raw)
In-Reply-To: <20250308034606.2036033-1-liumartin@google.com>
Hi Andrew,
I hope you've had a chance to review this patchset. I was wondering if you
had any concerns about merging it, or if there's anything I need to address.
Thanks,
Martin
On Sat, Mar 8, 2025 at 11:46 AM Martin Liu <liumartin@google.com> wrote:
>
> This patchset introduces tracepoints to track changes in the lowmem
> reserves, watermarks and totalreserve_pages. This helps to track
> the exact timing of such changes and understand their relation to
> reclaim activities.
>
> The tracepoints added are:
>
> mm_setup_per_zone_lowmem_reserve
> mm_setup_per_zone_wmarks
> mm_calculate_totalreserve_pagesi
>
> Changes in V2:
> Fix coding format error. Feedback from kaleshsingh@google.com.
>
> Martin Liu (3):
> mm/page_alloc: Add trace event for per-zone watermark setup
> mm/page_alloc: Add trace event for per-zone lowmem reserve setup
> mm/page_alloc: Add trace event for totalreserve_pages calculation
>
> include/trace/events/kmem.h | 78 +++++++++++++++++++++++++++++++++++++
> mm/page_alloc.c | 4 ++
> 2 files changed, 82 insertions(+)
>
> --
> 2.49.0.rc0.332.g42c0ae87b1-goog
>
prev parent reply other threads:[~2025-03-12 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 3:45 Martin Liu
2025-03-08 3:46 ` [PATCH v2 1/3] mm/page_alloc: Add trace event for per-zone watermark setup Martin Liu
2025-03-10 0:53 ` David Rientjes
2025-03-08 3:46 ` [PATCH v2 2/3] mm/page_alloc: Add trace event for per-zone lowmem reserve setup Martin Liu
2025-03-10 0:53 ` David Rientjes
2025-03-22 9:03 ` Steven Rostedt
2025-03-08 3:46 ` [PATCH v2 3/3] mm/page_alloc: Add trace event for totalreserve_pages calculation Martin Liu
2025-03-10 0:54 ` David Rientjes
2025-03-12 15:50 ` Martin Liu [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=CAASV4h4_xgJPZOvh8k5snJc_ocvwPih+SvK9D8+_Fid2chcz6Q@mail.gmail.com \
--to=liumartin@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=minchan@kernel.org \
--cc=rostedt@goodmis.org \
--cc=surenb@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