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 majord..
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,
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 sit
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
* 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 de
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.
>>
>
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 all
* 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.
> > >
>
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 performanc
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
> ca
* 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 hea
12 matches
Mail list logo
