From: Georgi Djakov <georgi.djakov@linaro.org>
To: Andrew Morton <akpm@linux-foundation.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: Fri, 13 Nov 2020 22:40:31 +0200 [thread overview]
Message-ID: <0e3179bc-61ad-19e4-9b19-956609e44e75@linaro.org> (raw)
In-Reply-To: <20201112111436.c5deeadd3578877fc0b844a1@linux-foundation.org>
On 11/12/20 21:14, Andrew Morton wrote:
> 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?
Thanks for the quick feedback. I'll add more details in the commit message
when i post v2 next week.
>
> Are there userspace tools which aid in the processing of this new
> information?
I'm not aware of any.
>
> Can/should Documentation/vm/page_owner.rst be updated?
Yeah, probably i should update at least the size of the objects.
>> --- 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?
Yes, indeed! Thank you!
BR,
Georgi
next prev parent reply other threads:[~2020-11-13 20:40 UTC|newest]
Thread overview: 8+ 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
2020-11-13 20:40 ` Georgi Djakov [this message]
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-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=0e3179bc-61ad-19e4-9b19-956609e44e75@linaro.org \
--to=georgi.djakov@linaro.org \
--cc=akpm@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).