linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arun Sharma <arun@sharma-home.net>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Can Hankendi <hankendi@gmail.com>, linux-perf-users@vger.kernel.org
Subject: Re: [perfmon2] updating perf tool
Date: Mon, 14 Feb 2011 12:08:28 -0800	[thread overview]
Message-ID: <AANLkTikfaAbdFWzcvayOjYLNECKf_L08nUUEWUy=p8it@mail.gmail.com> (raw)
In-Reply-To: <20110214194428.GE21384@ghostprotocols.net>

On Mon, Feb 14, 2011 at 11:44 AM, Arnaldo Carvalho de Melo
<acme@ghostprotocols.net> wrote:
>>
>> http://perfmon2.git.sourceforge.net/git/gitweb.cgi?p=perfmon2/libpfm4;a=blob;f=python/sys.py;h=e3a44f24174b979694e2588592f759010b77621e;hb=f70e032b5b69cf5aa6f7e0da746b1817c64341e9
>
> Interesting, have you seen the python binding in tip/perf/core?

My understanding of the stuff under scripts/python is that it links in
a python interpreter into perf and allows the user to write scripts to
filter the data coming in from the kernel.

The scripts I wrote a couple of years ago knew nothing about perf, the
user space tool and wrapped the syscall directly. Sample use case:
parse the hardware topology of a machine, understand how many NUMA
nodes/memory controllers there are in the system and print the
percentage of the memory bandwidth being used on each controller.

Potentially, perf itself could be structured as a set of shared
libraries, which are then glued together using a scripting language.
That may be the wrong trade-off for many users, who value simplicity
and efficiency of a tool written in C over scriptability. But such a
design could make activities such as parsing perf.data in a python
script essentially free.

 -Arun

  reply	other threads:[~2011-02-14 20:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTim5QGwisxLEHHHECrE1nLSYFxzXEMu7hvTRy09=@mail.gmail.com>
2011-02-11 19:44 ` [perfmon2] updating perf tool Arun Sharma
     [not found]   ` <AANLkTimqRjUTzv+AO7zHCfXvA1RZFDTjyb-r0s_MVNTW@mail.gmail.com>
2011-02-11 20:31     ` Arun Sharma
2011-02-14 19:44       ` Arnaldo Carvalho de Melo
2011-02-14 20:08         ` Arun Sharma [this message]
2011-02-14 20:48           ` Arnaldo Carvalho de Melo
2011-02-14 22:04             ` Arun Sharma
2011-02-15  1:24               ` Arnaldo Carvalho de Melo
2011-02-17 20:41                 ` Arun Sharma

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='AANLkTikfaAbdFWzcvayOjYLNECKf_L08nUUEWUy=p8it@mail.gmail.com' \
    --to=arun@sharma-home.net \
    --cc=acme@ghostprotocols.net \
    --cc=hankendi@gmail.com \
    --cc=linux-perf-users@vger.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 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).