From: Michal Hocko <mhocko@kernel.org>
To: Janani Ravichandran <janani.rvchndrn@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: Include postprocessing script for memory allocation tracing
Date: Fri, 21 Oct 2016 09:08:33 +0200 [thread overview]
Message-ID: <20161021070832.GE6045@dhcp22.suse.cz> (raw)
In-Reply-To: <4F0F918D-B98A-48EC-82ED-EE7D32F222EA@gmail.com>
On Thu 20-10-16 18:10:37, Janani Ravichandran wrote:
> Michal,
>
> > On Oct 18, 2016, at 8:13 AM, Michal Hocko <mhocko@kernel.org> wrote:
> >
> >>
> >
> > yes, function_graph tracer will give you _some_ information but it will
> > not have the context you are looking for, right? See the following
> > example
> >
> > ------------------------------------------
> > 0) x-www-b-22756 => x-termi-4083
> > ------------------------------------------
> >
> > 0) | __alloc_pages_nodemask() {
> > 0) | /* mm_page_alloc: page=ffffea000411b380 pfn=1066702 order=0 migratetype=0 gfp_flags=GFP_KERNEL */
> > 0) 3.328 us | }
> > 3) | __alloc_pages_nodemask() {
> > 3) | /* mm_page_alloc: page=ffffea0008f1f6c0 pfn=2344923 order=0 migratetype=0 gfp_flags=GFP_KERNEL */
> > 3) 1.011 us | }
> > 0) | __alloc_pages_nodemask() {
> > 0) | /* mm_page_alloc: page=ffffea000411b380 pfn=1066702 order=0 migratetype=0 gfp_flags=GFP_KERNEL */
> > 0) 0.587 us | }
> > 3) | __alloc_pages_nodemask() {
> > 3) | /* mm_page_alloc: page=ffffea0008f1f6c0 pfn=2344923 order=0 migratetype=0 gfp_flags=GFP_KERNEL */
> > 3) 1.125 us | }
> >
> > How do I know which process has performed those allocations? I know that
> > CPU0 should be running x-termi-4083 but what is running on other CPUs?
> >
> > Let me explain my usecase I am very interested in. Say I that a usespace
> > application is not performing well. I would like to see some statistics
> > about memory allocations performed for that app - are there few outliers
> > or the allocation stalls increase gradually? Where do we spend time during
> > that allocation? Reclaim LRU pages? Compaction or the slab shrinkers?
> >
> > To answer those questions I need to track particular events (alocation,
> > reclaim, compaction) to the process and know how long each step
> > took. Maybe we can reconstruct something from the above output but it is
> > a major PITA. If we either hard start/stop pairs for each step (which
> > we already do have for reclaim, compaction AFAIR) then this is an easy
> > scripting. Another option would be to have only a single tracepoint for
> > each step with a timing information.
> >
> > See my point?
>
> Yes, if we want to know what processes are running on what CPUs,
> echo funcgraph-proc > trace_options in the tracing directory should give us
> what we want.
Interesting.
$ cat /debug/tracing/available_tracers
function_graph preemptirqsoff preemptoff irqsoff function nop
Do I have to configure anything specially? And if I do why isn't it any
better to simply add a start tracepoint and make this available also to
older kernels?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2016-10-21 7:08 UTC|newest]
Thread overview: 15+ 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-12 12:16 ` Michal Hocko
2016-09-13 18:04 ` Janani Ravichandran
2016-09-19 9:42 ` Michal Hocko
2016-09-22 15:30 ` Janani Ravichandran
2016-09-23 8:07 ` Michal Hocko
2016-10-06 12:00 ` Michal Hocko
2016-10-11 14:43 ` Janani Ravichandran
2016-10-15 23:31 ` Janani Ravichandran
2016-10-16 7:33 ` Michal Hocko
[not found] ` <CANnt6X=RpSnuxGXZfF6Qa5mJpzC8gL3wkKJi3tQMZJBZJVWF3w@mail.gmail.com>
[not found] ` <A6E7231A-54FF-4D5C-90F5-0A8C4126CFEA@gmail.com>
2016-10-18 13:13 ` Michal Hocko
2016-10-20 23:10 ` Janani Ravichandran
2016-10-21 7:08 ` Michal Hocko [this message]
2016-10-27 15:42 ` Janani Ravichandran
-- strict thread matches above, loose matches on Subject: below --
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=20161021070832.GE6045@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=janani.rvchndrn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).