From: Andrew Morton <akpm@linux-foundation.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
sudaraja@codeaurora.org, pratikp@codeaurora.org,
lmark@codeaurora.org
Subject: Re: [PATCH] mm/page_owner: Record timestamp and pid
Date: Thu, 12 Nov 2020 11:14:36 -0800 [thread overview]
Message-ID: <20201112111436.c5deeadd3578877fc0b844a1@linux-foundation.org> (raw)
In-Reply-To: <20201112184106.733-1-georgi.djakov@linaro.org>
On Thu, 12 Nov 2020 20:41:06 +0200 Georgi Djakov <georgi.djakov@linaro.org> wrote:
> From: Liam Mark <lmark@codeaurora.org>
>
> Collect the time for each allocation recorded in page owner so that
> allocation "surges" can be measured.
>
> Record the pid for each allocation recorded in page owner so that
> the source of allocation "surges" can be better identified.
Please provide a description of why this is considered useful. What
has it been used for, what problems has it been used to solve?
Are there userspace tools which aid in the processing of this new
information?
Can/should Documentation/vm/page_owner.rst be updated?
> --- a/mm/page_owner.c
> +++ b/mm/page_owner.c
> @@ -10,6 +10,7 @@
> #include <linux/migrate.h>
> #include <linux/stackdepot.h>
> #include <linux/seq_file.h>
> +#include <linux/sched/clock.h>
>
> #include "internal.h"
>
> @@ -25,6 +26,8 @@ struct page_owner {
> gfp_t gfp_mask;
> depot_stack_handle_t handle;
> depot_stack_handle_t free_handle;
> + u64 ts_nsec;
> + int pid;
pid_t would be nicer?
next prev parent reply other threads:[~2020-11-12 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 18:41 [PATCH] mm/page_owner: Record timestamp and pid Georgi Djakov
2020-11-12 19:14 ` Andrew Morton [this message]
2020-11-13 20:40 ` Georgi Djakov
2020-11-27 17:52 ` Vlastimil Babka
2020-11-27 18:57 ` Georgi Djakov
2020-11-27 19:06 ` Vlastimil Babka
2020-11-27 19:23 ` Souptick Joarder
2020-11-27 19:23 ` Souptick Joarder
2020-11-30 12:04 ` Vlastimil Babka
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=20201112111436.c5deeadd3578877fc0b844a1@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lmark@codeaurora.org \
--cc=pratikp@codeaurora.org \
--cc=sudaraja@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.