Re: "perf top -g" leaking ~300MB per second.

2015-01-08 Thread Arnaldo Carvalho de Melo
Em Tue, Dec 30, 2014 at 02:38:13PM +0900, Namhyung Kim escreveu: > Subject: [PATCH] perf callchain: Free callchains when hist entries are deleted > Markus reported that "perf top -g" can leak ~300MB per second on his > machine. This is partly because it missed to free callchains when > hist entr

Re: "perf top -g" leaking ~300MB per second.

2014-12-30 Thread Arnaldo Carvalho de Melo
Em Tue, Dec 30, 2014 at 09:35:24AM +0100, Markus Trippelsdorf escreveu: > On 2014.12.30 at 14:38 +0900, Namhyung Kim wrote: > > Hi David and Markus, > > > > On Sat, Dec 13, 2014 at 11:16:43AM -0700, David Ahern wrote: > > > On 12/13/14 8:26 AM, Arnaldo Carvalho de Melo wrote: > > > >The callchain

Re: "perf top -g" leaking ~300MB per second.

2014-12-30 Thread Markus Trippelsdorf
On 2014.12.30 at 14:38 +0900, Namhyung Kim wrote: > Hi David and Markus, > > On Sat, Dec 13, 2014 at 11:16:43AM -0700, David Ahern wrote: > > On 12/13/14 8:26 AM, Arnaldo Carvalho de Melo wrote: > > >The callchain code was done initially for 'report' and when I made 'top' > > >reuse the hist_entry

Re: "perf top -g" leaking ~300MB per second.

2014-12-29 Thread Namhyung Kim
Hi David and Markus, On Sat, Dec 13, 2014 at 11:16:43AM -0700, David Ahern wrote: > On 12/13/14 8:26 AM, Arnaldo Carvalho de Melo wrote: > >The callchain code was done initially for 'report' and when I made 'top' > >reuse the hist_entry code allowing 'top' to collect callchains was too > >easy, bu

Re: "perf top -g" leaking ~300MB per second.

2014-12-13 Thread David Ahern
On 12/13/14 8:26 AM, Arnaldo Carvalho de Melo wrote: The callchain code was done initially for 'report' and when I made 'top' reuse the hist_entry code allowing 'top' to collect callchains was too easy, but then we need to go thru the callchain/hists/hist_entry code to make sure that they don't l

Re: "perf top -g" leaking ~300MB per second.

2014-12-13 Thread Arnaldo Carvalho de Melo
Em Sat, Dec 13, 2014 at 10:03:31AM +0100, Markus Trippelsdorf escreveu: > On 2014.12.13 at 09:48 +0100, Markus Trippelsdorf wrote: > > Running "perf top -g" built from current Linus tree apparently leaks > > ~300MB of memory every second an my machine. > > Hmm, this is a much older problem. I just

Re: "perf top -g" leaking ~300MB per second.

2014-12-13 Thread Markus Trippelsdorf
On 2014.12.13 at 09:48 +0100, Markus Trippelsdorf wrote: > Running "perf top -g" built from current Linus tree apparently leaks > ~300MB of memory every second an my machine. Hmm, this is a much older problem. I just noticed this the first time today. To reproduce: Compile some application in the

"perf top -g" leaking ~300MB per second.

2014-12-13 Thread Markus Trippelsdorf
Running "perf top -g" built from current Linus tree apparently leaks ~300MB of memory every second an my machine. -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.o