All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Schuchart <joseph.schuchart@tu-dresden.de>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	thomas.ilsche@tu-dresden.de, linux-kernel@vger.kernel.org,
	Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: Perf Python Scripting Leaks Memory
Date: Thu, 24 Oct 2013 08:09:58 +0200	[thread overview]
Message-ID: <5268B9B6.40809@tu-dresden.de> (raw)
In-Reply-To: <20131023200149.GA6539@ghostprotocols.net>

On 23.10.2013 22:01, Arnaldo Carvalho de Melo wrote:
> Em Wed, Oct 23, 2013 at 04:37:41PM +0200, Joseph Schuchart escreveu:
>>    We are using the Python scripting interface in perf to extract kernel
>>    events relevant for performance analysis of HPC codes. We noticed that the
>>    "perf script" call allocates a significant amount of memory (in the order
>>    of several 100 MiB) during it's run, e.g. 125 MiB for a 25 MiB input file:
> 
> Thanks for the analysis and the bug fix!
> 
> I asked Tom Zanussi and he kindly reviewed your patch and provided an
> Acked-by tag for it, Tom, may I add a Reviewed-by: as well?
> 
> Joseph, can I have your Signed-off-by: tag, as documented in:
> 
> Documentation/SubmittingPatches
> 

Thanks for your quick reply and sorry for not following the
recommendations in the documentation.

Signed-off-by: Joseph Schuchart <joseph.schuchart@tu-dresden.de>

Thanks!
Joseph

      parent reply	other threads:[~2013-10-24  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5267DF35.5010706@tu-dresden.de>
2013-10-23 20:01 ` Perf Python Scripting Leaks Memory Arnaldo Carvalho de Melo
2013-10-23 20:04   ` Tom Zanussi
2013-10-24  6:09   ` Joseph Schuchart [this message]

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=5268B9B6.40809@tu-dresden.de \
    --to=joseph.schuchart@tu-dresden.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=thomas.ilsche@tu-dresden.de \
    --cc=tom.zanussi@linux.intel.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 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.