public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SUVONOV BUNYOD <b.suvonov@sjtu.edu.cn>
To: akpm <akpm@linux-foundation.org>,
	vbabka@kernel.org,  linux-mm <linux-mm@kvack.org>
Cc: rostedt <rostedt@goodmis.org>, mhiramat <mhiramat@kernel.org>,
	 mathieu desnoyers <mathieu.desnoyers@efficios.com>,
	 linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	surenb@google.com,  mhocko@suse.com, jackmanb@google.com,
	hannes <hannes@cmpxchg.org>,
	 ziy@nvidia.com, david <david@kernel.org>,
	 vishal moola <vishal.moola@gmail.com>,
	corbet@lwn.net,  skhan@linuxfoundation.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] mm/page_alloc: trace PCP refills and PCP zone lock usage
Date: Mon, 27 Apr 2026 14:21:05 +0800 (CST)	[thread overview]
Message-ID: <222049437.2315342.1777270865090.JavaMail.zimbra@sjtu.edu.cn> (raw)
In-Reply-To: <20260427060142.131055-1-b.suvonov@sjtu.edu.cn>

Thank you for reviewing v1 Vishal,

All of your concerns except for the last one should be covered in v2.

> If you're trying to trace all pages as they come onto the pcp lists,
> should you also account for the free_frozen_page_commit() path?
>
>>          }
>>          spin_unlock_irqrestore(&zone->lock, flags);

No, the intent is not to trace every insertion into PCP lists. This patch
is trying to make buddy <-> PCP traffic observable by adding a new
mm_page_pcpu_refill event symmetric with the existing mm_page_pcpu_drain
event.

I also added additional zone_locked tracepoints because my research is
focusing on analyzing which kernel mm subsystems and other parts are
under stress for a given workload. The best way to see it for PCP would
be to count zone lock acquirings as the whole purpose of PCP is to lower
number of zone lock acquiring in first place.

  reply	other threads:[~2026-04-27  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-25  9:13 [PATCH] mm/page_alloc: add tracepoint for PCP refills Bunyod Suvonov
2026-04-26 22:06 ` Vishal Moola
2026-04-27  6:01 ` [PATCH v2] mm/page_alloc: trace PCP refills and PCP zone lock usage Bunyod Suvonov
2026-04-27  6:21   ` SUVONOV BUNYOD [this message]
2026-04-28 18:23   ` Steven Rostedt
2026-04-29  3:31     ` SUVONOV BUNYOD
2026-04-29 14:52       ` Steven Rostedt

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=222049437.2315342.1777270865090.JavaMail.zimbra@sjtu.edu.cn \
    --to=b.suvonov@sjtu.edu.cn \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=jackmanb@google.com \
    --cc=linux-doc@vger.kernel.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=mhocko@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=vishal.moola@gmail.com \
    --cc=ziy@nvidia.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