From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Li Zefan <lizf@cn.fujitsu.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool
Date: Mon, 23 Nov 2009 18:53:30 +0100 [thread overview]
Message-ID: <20091123175330.GA29396@elte.hu> (raw)
In-Reply-To: <1258987585.22249.1036.camel@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 2009-11-20 at 11:49 +0100, Ingo Molnar wrote:
> > >
> > > You're right, of course. With kmemtrace-user, I just copied the raw
> > > trace file from /sys/kernel. I wonder if that's a good enough reason
> > > to keep kmemtrace bits around?
> >
> > Not really. If then a light-weight recording app could be made but
> > i'd rather wait for actual usecases to pop up.
>
> Hmm, but isn't this an actual use case?
Not really - perf record is pretty lightweight and you'd want perf for
hands-on stats anyway.
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Li Zefan <lizf@cn.fujitsu.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC][PATCH 1/2] perf: Add 'perf kmem' tool
Date: Mon, 23 Nov 2009 18:53:30 +0100 [thread overview]
Message-ID: <20091123175330.GA29396@elte.hu> (raw)
In-Reply-To: <1258987585.22249.1036.camel@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 2009-11-20 at 11:49 +0100, Ingo Molnar wrote:
> > >
> > > You're right, of course. With kmemtrace-user, I just copied the raw
> > > trace file from /sys/kernel. I wonder if that's a good enough reason
> > > to keep kmemtrace bits around?
> >
> > Not really. If then a light-weight recording app could be made but
> > i'd rather wait for actual usecases to pop up.
>
> Hmm, but isn't this an actual use case?
Not really - perf record is pretty lightweight and you'd want perf for
hands-on stats anyway.
Ingo
--
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>
next prev parent reply other threads:[~2009-11-23 17:53 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 7:53 [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Li Zefan
2009-11-20 7:53 ` Li Zefan
2009-11-20 7:53 ` [PATCH 2/2] tracing: Remove kmemtrace tracer Li Zefan
2009-11-20 7:53 ` Li Zefan
2009-11-20 8:20 ` Pekka Enberg
2009-11-20 8:20 ` Pekka Enberg
2009-11-20 8:24 ` Li Zefan
2009-11-20 8:24 ` Li Zefan
2009-11-20 8:27 ` Pekka Enberg
2009-11-20 8:27 ` Pekka Enberg
2009-11-20 8:31 ` Li Zefan
2009-11-20 8:31 ` Li Zefan
2009-11-20 8:14 ` [RFC][PATCH 1/2] perf: Add 'perf kmem' tool Ingo Molnar
2009-11-20 8:14 ` Ingo Molnar
2009-11-20 8:19 ` Pekka Enberg
2009-11-20 8:19 ` Pekka Enberg
2009-11-20 8:30 ` Ingo Molnar
2009-11-20 8:30 ` Ingo Molnar
2009-11-20 8:47 ` Pekka Enberg
2009-11-20 8:47 ` Pekka Enberg
2009-11-20 8:53 ` Li Zefan
2009-11-20 8:53 ` Li Zefan
2009-11-20 9:03 ` Ingo Molnar
2009-11-20 9:03 ` Ingo Molnar
2009-11-20 9:14 ` Li Zefan
2009-11-20 9:14 ` Li Zefan
2009-11-20 14:42 ` Arnaldo Carvalho de Melo
2009-11-20 14:42 ` Arnaldo Carvalho de Melo
2009-11-20 16:41 ` Ingo Molnar
2009-11-20 16:41 ` Ingo Molnar
2009-11-20 17:52 ` Arnaldo Carvalho de Melo
2009-11-20 17:52 ` Arnaldo Carvalho de Melo
2009-11-23 6:51 ` Ingo Molnar
2009-11-23 6:51 ` Ingo Molnar
2009-11-23 7:22 ` Peter Zijlstra
2009-11-23 7:22 ` Peter Zijlstra
2009-11-23 7:33 ` Ingo Molnar
2009-11-23 7:33 ` Ingo Molnar
2009-11-23 14:37 ` Arnaldo Carvalho de Melo
2009-11-23 14:37 ` Arnaldo Carvalho de Melo
2009-11-23 14:32 ` Arnaldo Carvalho de Melo
2009-11-23 14:32 ` Arnaldo Carvalho de Melo
2009-11-20 9:01 ` Ingo Molnar
2009-11-20 9:01 ` Ingo Molnar
2009-11-20 9:15 ` Pekka Enberg
2009-11-20 9:15 ` Pekka Enberg
2009-11-20 10:13 ` Ingo Molnar
2009-11-20 10:13 ` Ingo Molnar
2009-11-20 10:31 ` Pekka Enberg
2009-11-20 10:31 ` Pekka Enberg
2009-11-20 10:49 ` Ingo Molnar
2009-11-20 10:49 ` Ingo Molnar
2009-11-23 14:46 ` Steven Rostedt
2009-11-23 14:46 ` Steven Rostedt
2009-11-23 17:53 ` Ingo Molnar [this message]
2009-11-23 17:53 ` Ingo Molnar
2009-11-20 8:20 ` Li Zefan
2009-11-20 8:20 ` Li Zefan
2009-11-20 8:54 ` [tip:perf/core] " tip-bot for Li Zefan
2009-11-20 8:54 ` tip-bot for Li Zefan
2009-11-20 8:55 ` [RFC][PATCH 1/2] " Ingo Molnar
2009-11-20 8:55 ` Ingo Molnar
2009-11-20 9:11 ` Li Zefan
2009-11-20 9:11 ` Li Zefan
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=20091123175330.GA29396@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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.