linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Janani Ravichandran <janani.rvchndrn@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: riel@surriel.com, akpm@linux-foundation.org, hannes@compxchg.org,
	vdavydov@virtuozzo.com, mhocko@suse.com, vbabka@suse.cz,
	mgorman@techsingularity.net, kirill.shutemov@linux.intel.com,
	bywxiaobai@163.com, rostedt@goodmis.org
Subject: [PATCH 0/2] New tracepoints for slowpath and memory compaction
Date: Wed, 27 Jul 2016 10:43:07 -0400	[thread overview]
Message-ID: <cover.1469629027.git.janani.rvchndrn@gmail.com> (raw)

Hi,

I am an Outreachy intern working under Rik van Riel on memory allocation 
latency tracing using tracepoints.
The goal of my project is to add tracepoints to code in vmscan.c and 
compaction.c to gain insight into what happens there and examine latencies
using a postprocessing script.

The one here:

https://github.com/Jananiravichandran/Analyzing-tracepoints/blob/master/shrink_slab_latencies.py

is a very basic script that shows how long direct reclaim and shrinkers take.
I intend to keep updating the script as more tracepoints are added in
the direct reclaim and compaction code and eventually submit the script
itself once I'm done.
Suggestions on this are most welcome! 

As of now, there are no mechanisms to find out how long slowpath and
memory compaction take to execute. This patchset adds new tracepoints 
and also modifies a couple of existing ones to address this and collect
some zone information that may be useful.

Janani Ravichandran (2):
  mm: page_alloc.c: Add tracepoints for slowpath
  mm: compaction.c: Add/Modify direct compaction tracepoints

 include/trace/events/compaction.h | 38 ++++++++++++++++++++++++++++++++-----
 include/trace/events/kmem.h       | 40 +++++++++++++++++++++++++++++++++++++++
 mm/compaction.c                   |  6 ++++--
 mm/page_alloc.c                   |  5 +++++
 4 files changed, 82 insertions(+), 7 deletions(-)

-- 
2.7.0

             reply	other threads:[~2016-07-27 14:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 14:43 Janani Ravichandran [this message]
2016-07-27 14:47 ` [PATCH 1/2] mm: page_alloc.c: Add tracepoints for slowpath Janani Ravichandran
2016-07-27 15:23   ` Steven Rostedt
2016-07-27 17:20     ` Dave Hansen
2016-07-27 17:30       ` Steven Rostedt
2016-07-28 20:11     ` Janani Ravichandran
2016-08-04 15:19       ` Steven Rostedt
2016-08-05 16:03         ` Janani Ravichandran
2016-08-05 16:30           ` Steven Rostedt
2016-08-07 10:36             ` Janani Ravichandran
2016-07-27 16:33   ` Michal Hocko
2016-07-27 18:16     ` Rik van Riel
2016-07-27 18:28       ` Steven Rostedt
2016-07-27 18:44       ` Michal Hocko
2016-07-27 18:57         ` Rik van Riel
2016-07-27 14:51 ` [PATCH 2/2] mm: compaction.c: Add/Modify direct compaction tracepoints Janani Ravichandran
2016-07-27 15:24   ` Steven Rostedt
2016-08-01 13:25   ` Vlastimil Babka
2016-08-07 12:32     ` 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=cover.1469629027.git.janani.rvchndrn@gmail.com \
    --to=janani.rvchndrn@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bywxiaobai@163.com \
    --cc=hannes@compxchg.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=riel@surriel.com \
    --cc=rostedt@goodmis.org \
    --cc=vbabka@suse.cz \
    --cc=vdavydov@virtuozzo.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;
as well as URLs for NNTP newsgroup(s).