From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Valdis.Kletnieks@vt.edu
Subject: Re: perf: "Longum est iter per praecepta, breve et efficax per exempla"
Date: Thu, 6 Aug 2009 10:32:19 +0200 [thread overview]
Message-ID: <20090806083219.GA4163@Pilar.aei.mpg.de> (raw)
In-Reply-To: <84144f020908060008x34a320e2nc6a6bf8a665e51b4@mail.gmail.com>
Hi Pekka,
On Thu 6.Aug'09 at 10:08:44 +0300, Pekka Enberg wrote:
> Hi Carlos,
>
> On Wed, Aug 5, 2009 at 9:53 PM, Carlos R. Mafra<crmafra2@gmail.com> wrote:
> > A few examples of how 'perf' can be used, from an e-mail by
> > Ingo Molnar http://lkml.org/lkml/2009/8/4/346.
> >
> > Signed-off-by: Carlos R. Mafra <crmafra2@gmail.com>
> > ---
> >
> > This "patch" is my way of _suggesting_ some "documentation by examples"
> > of what 'perf' can do to the guys who can really write it :-)
>
> I was also looking for a perf "cookbook" and Ingo suggested we should
> put this stuff on the kernel.org wiki:
>
> http://perf.wiki.kernel.org/index.php/Main_Page
>
> How about just putting the email there?
First of all I just would like to rephrase my comment in the patch.
It was not meant to be a suggestion for Ingo to write more documentation
per se, it was my way of pointing out that such "documentation" is
useful for beginners and that I, as Valdis, appreciated reading it.
So it was more of a "keep coming" and don't rephrain from writing these
examples in the e-mails kind of thing.
Now about the wiki. Yeah, that sounds great and I didn't know about it
yesterday. It will be nice if the wiki becomes a place where people
can look for such usage examples.
Thanks for the attention,
Carlos
next prev parent reply other threads:[~2009-08-06 8:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 18:12 [PATCH 0/4] Add some trace events for the page allocator v3 Mel Gorman
2009-08-04 18:12 ` [PATCH 1/4] tracing, page-allocator: Add trace events for page allocation and page freeing Mel Gorman
2009-08-05 9:13 ` KOSAKI Motohiro
2009-08-05 9:40 ` Mel Gorman
2009-08-07 1:17 ` KOSAKI Motohiro
2009-08-07 17:31 ` Mel Gorman
2009-08-08 5:44 ` KOSAKI Motohiro
2009-08-04 18:12 ` [PATCH 2/4] tracing, mm: Add trace events for anti-fragmentation falling back to other migratetypes Mel Gorman
2009-08-05 9:26 ` KOSAKI Motohiro
2009-08-04 18:12 ` [PATCH 3/4] tracing, page-allocator: Add trace event for page traffic related to the buddy lists Mel Gorman
2009-08-05 9:24 ` KOSAKI Motohiro
2009-08-05 9:43 ` Mel Gorman
2009-08-07 1:03 ` KOSAKI Motohiro
2009-08-04 18:12 ` [PATCH 4/4] tracing, page-allocator: Add a postprocessing script for page-allocator-related ftrace events Mel Gorman
2009-08-04 18:22 ` Andrew Morton
2009-08-04 18:27 ` Rik van Riel
2009-08-04 19:13 ` Andrew Morton
2009-08-04 20:48 ` Mel Gorman
2009-08-05 7:41 ` Ingo Molnar
2009-08-05 9:07 ` Mel Gorman
2009-08-05 9:16 ` Ingo Molnar
2009-08-05 10:27 ` Johannes Weiner
2009-08-06 15:48 ` Mel Gorman
2009-08-05 14:53 ` Larry Woodman
2009-08-06 15:54 ` Mel Gorman
2009-08-04 19:57 ` Ingo Molnar
2009-08-04 20:18 ` Andrew Morton
2009-08-04 20:35 ` Ingo Molnar
2009-08-04 20:53 ` Andrew Morton
2009-08-05 7:53 ` Ingo Molnar
2009-08-05 13:04 ` Peter Zijlstra
2009-08-05 15:07 ` Valdis.Kletnieks
2009-08-05 14:53 ` Valdis.Kletnieks
2009-08-05 18:53 ` perf: "Longum est iter per praecepta, breve et efficax per exempla" Carlos R. Mafra
2009-08-06 7:08 ` Pekka Enberg
2009-08-06 7:35 ` Ingo Molnar
2009-08-06 8:38 ` Carlos R. Mafra
2009-08-06 8:32 ` Carlos R. Mafra [this message]
2009-08-06 9:10 ` Ingo Molnar
2009-08-08 12:37 ` [tip:perfcounters/urgent] " tip-bot for Carlos R. Mafra
2009-08-09 11:11 ` [tip:perfcounters/core] " tip-bot for Carlos R. Mafra
2009-08-06 15:50 ` [PATCH 4/4] tracing, page-allocator: Add a postprocessing script for page-allocator-related ftrace events Mel Gorman
2009-08-05 3:07 ` KOSAKI Motohiro
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=20090806083219.GA4163@Pilar.aei.mpg.de \
--to=crmafra2@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®