All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Minchan Kim <minchan@kernel.org>,
	Joonsoo Kim <js1304@gmail.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCHSET 0/6] perf kmem: Implement page allocation analysis (v7)
Date: Tue, 14 Apr 2015 08:36:21 +0300	[thread overview]
Message-ID: <CAOJsxLF8gZ2xHRQY7vX45_=hE_9r=HNsoA_3Le5jK==V2WG7Xg@mail.gmail.com> (raw)
In-Reply-To: <1428979956-23667-1-git-send-email-namhyung@kernel.org>

On Tue, Apr 14, 2015 at 5:52 AM, Namhyung Kim <namhyung@kernel.org> wrote:
> Currently perf kmem command only analyzes SLAB memory allocation.  And
> I'd like to introduce page allocation analysis also.  Users can use
>  --slab and/or --page option to select it.  If none of these options
>  are used, it does slab allocation analysis for backward compatibility.

Nice addition!

Acked-by: Pekka Enberg <penberg@kernel.org>

for the whole series.

- Pekka

WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Minchan Kim <minchan@kernel.org>,
	Joonsoo Kim <js1304@gmail.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCHSET 0/6] perf kmem: Implement page allocation analysis (v7)
Date: Tue, 14 Apr 2015 08:36:21 +0300	[thread overview]
Message-ID: <CAOJsxLF8gZ2xHRQY7vX45_=hE_9r=HNsoA_3Le5jK==V2WG7Xg@mail.gmail.com> (raw)
In-Reply-To: <1428979956-23667-1-git-send-email-namhyung@kernel.org>

On Tue, Apr 14, 2015 at 5:52 AM, Namhyung Kim <namhyung@kernel.org> wrote:
> Currently perf kmem command only analyzes SLAB memory allocation.  And
> I'd like to introduce page allocation analysis also.  Users can use
>  --slab and/or --page option to select it.  If none of these options
>  are used, it does slab allocation analysis for backward compatibility.

Nice addition!

Acked-by: Pekka Enberg <penberg@kernel.org>

for the whole series.

- Pekka

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2015-04-14  5:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14  2:52 [PATCHSET 0/6] perf kmem: Implement page allocation analysis (v7) Namhyung Kim
2015-04-14  2:52 ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 1/6] perf kmem: Implement stat --page --caller Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 2/6] perf kmem: Support sort keys on page analysis Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 3/6] perf kmem: Add --live option for current allocation stat Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 4/6] perf kmem: Print gfp flags in human readable string Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 5/6] perf kmem: Add kmem.default config option Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  2:52 ` [PATCH 6/6] perf kmem: Show warning when trying to run stat without record Namhyung Kim
2015-04-14  2:52   ` Namhyung Kim
2015-04-14  5:36 ` Pekka Enberg [this message]
2015-04-14  5:36   ` [PATCHSET 0/6] perf kmem: Implement page allocation analysis (v7) Pekka Enberg

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='CAOJsxLF8gZ2xHRQY7vX45_=hE_9r=HNsoA_3Le5jK==V2WG7Xg@mail.gmail.com' \
    --to=penberg@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@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.