From: Janani Ravichandran <janani.rvchndrn@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Janani Ravichandran <janani.rvchndrn@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: Include postprocessing script for memory allocation tracing
Date: Mon, 17 Oct 2016 13:31:57 -0400 [thread overview]
Message-ID: <A6E7231A-54FF-4D5C-90F5-0A8C4126CFEA@gmail.com> (raw)
In-Reply-To: <CANnt6X=RpSnuxGXZfF6Qa5mJpzC8gL3wkKJi3tQMZJBZJVWF3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
> On Oct 17, 2016, at 1:24 PM, Janani Ravichandran <janani.rvchndrn@gmail.com> wrote:
>
>
> On Sun, Oct 16, 2016 at 3:33 AM, Michal Hocko <mhocko@kernel.org <mailto:mhocko@kernel.org>> wrote:
>
> trace_mm_page_alloc will tell you details about the allocation, like
> gfp mask, order but it doesn't tell you how long the allocation took at
> its current form. So either you have to note jiffies at the allocation
> start and then add the end-start in the trace point or we really need
> another trace point to note the start. The later has an advantage that
> we do not add unnecessary load for jiffies when the tracepoint is
> disabled.
The function graph tracer can tell us how long alloc_pages_nodemask() took.
Can’t that, combined with the context information given by trace_mm_page_alloc
give us what we want? Correct me if I am wrong.
Regards,
Janani.
> --
> Michal Hocko
> SUSE Labs
>
[-- Attachment #2: Type: text/html, Size: 2169 bytes --]
next prev parent reply other threads:[~2016-10-17 17:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 22:24 [RFC] scripts: Include postprocessing script for memory allocation tracing Janani Ravichandran
2016-09-11 22:24 ` Janani Ravichandran
2016-09-12 12:16 ` Michal Hocko
2016-09-12 12:16 ` Michal Hocko
2016-09-13 18:04 ` Janani Ravichandran
2016-09-13 18:04 ` Janani Ravichandran
2016-09-19 9:42 ` Michal Hocko
2016-09-19 9:42 ` Michal Hocko
2016-09-22 15:30 ` Janani Ravichandran
2016-09-22 15:30 ` Janani Ravichandran
2016-09-23 8:07 ` Michal Hocko
2016-09-23 8:07 ` Michal Hocko
2016-10-06 12:00 ` Michal Hocko
2016-10-06 12:00 ` Michal Hocko
2016-10-11 14:43 ` Janani Ravichandran
2016-10-11 14:43 ` Janani Ravichandran
2016-10-15 23:31 ` Janani Ravichandran
2016-10-15 23:31 ` Janani Ravichandran
2016-10-16 7:33 ` Michal Hocko
2016-10-16 7:33 ` Michal Hocko
[not found] ` <CANnt6X=RpSnuxGXZfF6Qa5mJpzC8gL3wkKJi3tQMZJBZJVWF3w@mail.gmail.com>
2016-10-17 17:31 ` Janani Ravichandran [this message]
2016-10-18 13:13 ` Michal Hocko
2016-10-18 13:13 ` Michal Hocko
2016-10-20 23:10 ` Janani Ravichandran
2016-10-20 23:10 ` Janani Ravichandran
2016-10-21 7:08 ` Michal Hocko
2016-10-21 7:08 ` Michal Hocko
2016-10-27 15:42 ` Janani Ravichandran
2016-10-27 15:42 ` Janani Ravichandran
-- strict thread matches above, loose matches on Subject: below --
2016-08-19 11:38 Janani Ravichandran
2016-08-19 11:38 ` Janani Ravichandran
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=A6E7231A-54FF-4D5C-90F5-0A8C4126CFEA@gmail.com \
--to=janani.rvchndrn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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.