Hi Arnaldo,
Thanks for your work! I'm gonna be offline this week as it's one of
the biggest holyday in Korea (and other Asian countries). I'll catch
up next week.
--
Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Em Wed, Sep 18, 2013 at 12:12:53PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
> > > On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > > >
Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
> > On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > > * Frederic Weisbecker wrote:
> > >> My patches and Namhyung's should improve the comm
Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
> Hi Ingo,
>
> On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > * Frederic Weisbecker wrote:
> >> My patches and Namhyung's should improve the comm situation a lot but we
> >> can't do much miracle. The only way would be
Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
Hi Ingo,
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
My patches and Namhyung's should improve the comm situation a lot but we
can't do much miracle. The only way
Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
My patches and Namhyung's should improve the
Em Wed, Sep 18, 2013 at 12:12:53PM -0300, Arnaldo Carvalho de Melo escreveu:
Em Wed, Sep 18, 2013 at 11:20:38AM -0300, Arnaldo Carvalho de Melo escreveu:
Em Tue, Sep 17, 2013 at 02:54:22PM +0900, Namhyung Kim escreveu:
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
Well, it was
Hi Arnaldo,
Thanks for your work! I'm gonna be offline this week as it's one of
the biggest holyday in Korea (and other Asian countries). I'll catch
up next week.
--
Thanks,
Namhyung
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
* Namhyung Kim wrote:
> Hi Ingo,
>
> On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> > * Frederic Weisbecker wrote:
> >> My patches and Namhyung's should improve the comm situation a lot but we
> >> can't do much miracle. The only way would be perhaps to be able to limit
> >> the
* Namhyung Kim namhy...@kernel.org wrote:
Hi Ingo,
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
My patches and Namhyung's should improve the comm situation a lot but we
can't do much miracle. The only way would be perhaps to be
Hi Ingo,
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
> * Frederic Weisbecker wrote:
>> My patches and Namhyung's should improve the comm situation a lot but we
>> can't do much miracle. The only way would be perhaps to be able to limit
>> the deepness of the callchain branches.
>>
Hi Ingo,
On Sat, 14 Sep 2013 08:11:49 +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
My patches and Namhyung's should improve the comm situation a lot but we
can't do much miracle. The only way would be perhaps to be able to limit
the deepness of the callchain
On 9/13/13 5:43 AM, Frederic Weisbecker wrote:
The only way would be perhaps to be able to limit the deepness
of the callchain branches.
I was thinking about such a feature two days ago. Max callchain depth is
set to 255 at compile time which can generate huge event sizes. perf
needs to
* Frederic Weisbecker wrote:
> On Thu, Sep 12, 2013 at 10:36:58PM +0200, Ingo Molnar wrote:
> >
> > * Frederic Weisbecker wrote:
> >
> > > The way we handle hists sorted by comm is to first gather them by tid
> > > then in the end merge/collapse hists that end up with the same comm.
> > >
* Frederic Weisbecker fweis...@gmail.com wrote:
On Thu, Sep 12, 2013 at 10:36:58PM +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
The way we handle hists sorted by comm is to first gather them by tid
then in the end merge/collapse hists that end up with
On 9/13/13 5:43 AM, Frederic Weisbecker wrote:
The only way would be perhaps to be able to limit the deepness
of the callchain branches.
I was thinking about such a feature two days ago. Max callchain depth is
set to 255 at compile time which can generate huge event sizes. perf
needs to
On Fri, Sep 13, 2013 at 03:32:34PM +0900, Namhyung Kim wrote:
> Hi Frederic,
>
> On Thu, 12 Sep 2013 22:29:39 +0200, Frederic Weisbecker wrote:
> > The way we handle hists sorted by comm is to first gather them by tid then
> > in the end merge/collapse hists that end up with the same comm.
> >
>
On Thu, Sep 12, 2013 at 10:36:58PM +0200, Ingo Molnar wrote:
>
> * Frederic Weisbecker wrote:
>
> > The way we handle hists sorted by comm is to first gather them by tid
> > then in the end merge/collapse hists that end up with the same comm.
> >
> > But merging hists has shown some
Hi Frederic,
On Thu, 12 Sep 2013 22:29:39 +0200, Frederic Weisbecker wrote:
> The way we handle hists sorted by comm is to first gather them by tid then
> in the end merge/collapse hists that end up with the same comm.
>
> But merging hists has shown some performances issues, especially with
>
Hi Frederic,
On Thu, 12 Sep 2013 22:29:39 +0200, Frederic Weisbecker wrote:
The way we handle hists sorted by comm is to first gather them by tid then
in the end merge/collapse hists that end up with the same comm.
But merging hists has shown some performances issues, especially with
On Thu, Sep 12, 2013 at 10:36:58PM +0200, Ingo Molnar wrote:
* Frederic Weisbecker fweis...@gmail.com wrote:
The way we handle hists sorted by comm is to first gather them by tid
then in the end merge/collapse hists that end up with the same comm.
But merging hists has shown some
On Fri, Sep 13, 2013 at 03:32:34PM +0900, Namhyung Kim wrote:
Hi Frederic,
On Thu, 12 Sep 2013 22:29:39 +0200, Frederic Weisbecker wrote:
The way we handle hists sorted by comm is to first gather them by tid then
in the end merge/collapse hists that end up with the same comm.
But
The way we handle hists sorted by comm is to first gather them by tid then
in the end merge/collapse hists that end up with the same comm.
But merging hists has shown some performances issues, especially with callchain
where the operation can be very heavy.
So this new comm infrastructure aims
* Frederic Weisbecker wrote:
> The way we handle hists sorted by comm is to first gather them by tid
> then in the end merge/collapse hists that end up with the same comm.
>
> But merging hists has shown some performances issues, especially with
> callchain where the operation can be very
The way we handle hists sorted by comm is to first gather them by tid then
in the end merge/collapse hists that end up with the same comm.
But merging hists has shown some performances issues, especially with callchain
where the operation can be very heavy.
So this new comm infrastructure aims
* Frederic Weisbecker fweis...@gmail.com wrote:
The way we handle hists sorted by comm is to first gather them by tid
then in the end merge/collapse hists that end up with the same comm.
But merging hists has shown some performances issues, especially with
callchain where the operation
26 matches
Mail list logo
