[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181119071647.GC20153@sejong>
Date: Mon, 19 Nov 2018 16:16:47 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: David Miller <davem@...emloft.net>
Cc: jolsa@...hat.com, acme@...nel.org, linux-kernel@...r.kernel.org,
jolsa@...nel.org, kernel-team@....com
Subject: Re: [PATCH RFC] hist lookups
On Sun, Nov 18, 2018 at 10:33:55PM -0800, David Miller wrote:
> From: Namhyung Kim <namhyung@...nel.org>
> Date: Mon, 19 Nov 2018 15:28:37 +0900
>
> > Hello David,
> >
> > On Sun, Nov 18, 2018 at 08:52:43PM -0800, David Miller wrote:
> >> From: Jiri Olsa <jolsa@...hat.com>
> >> Date: Tue, 13 Nov 2018 11:40:54 +0100
> >>
> >> > I pushed/rebased what I have to perf/fixes branch again
> >> >
> >> > please note I had to change our compile changes, because
> >> > they wouldn't compile on x86, but I can't verify on sparc,
> >> > so you might see some compile fails again
> >>
> >> I just checked your current perf/fixes branch.
> >>
> >> It builds on Sparc ;-)
> >>
> >> And it behaves better too. I do get tons of drops and lost events,
> >> but it seems to keep going even during the hardest load.
> >>
> >> Eventually I end up with a lot of unresolvable histogram entries,
> >> so that is something to look into.
> >
> > Did you record callchains as well? I'd like to know whether it's
> > related to the children (cumulative) mode or not.
>
> I did not have callchains on, just plain "./perf top"
OK, I need to think about it more..
Thanks,
Namhyung
Powered by blists - more mailing lists