From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH 0/3] perf hists: Changes on hists__{link,match}
Date: Tue, 4 Dec 2012 14:54:55 +0100 [thread overview]
Message-ID: <20121204135454.GA1041@krava.brq.redhat.com> (raw)
In-Reply-To: <1354596265-9901-1-git-send-email-namhyung@kernel.org>
On Tue, Dec 04, 2012 at 01:44:22PM +0900, Namhyung Kim wrote:
> Hi Arnaldo,
>
> This is what I talked to Jiri yesterday, and it can be a common basis
> of both event group and multiple diff patchset. The point is using
> internal input or collapsed rb tree to sort hist entries rather than
> output tree with unnessary resort.
>
> Please take a look.
>
> Thanks,
> Namhyung
>
>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Stephane Eranian <eranian@google.com>
> Cc: Namhyung Kim <namhyung.kim@lge.com>
>
> Namhyung Kim (3):
> perf hists: Exchange order of comparing items when collapsing hists
> perf hists: Link hist entries before inserting to an output tree
> perf diff: Use internal rb tree for compute resort
hi,
could you please push branch with this?
thanks,
jirka
prev parent reply other threads:[~2012-12-04 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 4:44 Namhyung Kim
2012-12-04 4:44 ` [PATCH 1/3] perf hists: Exchange order of comparing items when collapsing hists Namhyung Kim
2012-12-04 13:44 ` Arnaldo Carvalho de Melo
2012-12-04 14:57 ` Namhyung Kim
2012-12-04 4:44 ` [PATCH 2/3] perf hists: Link hist entries before inserting to an output tree Namhyung Kim
2012-12-04 4:44 ` [PATCH 3/3] perf diff: Use internal rb tree for compute resort Namhyung Kim
2012-12-04 13:45 ` Arnaldo Carvalho de Melo
2012-12-04 15:03 ` Namhyung Kim
2012-12-04 13:54 ` Jiri Olsa [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=20121204135454.GA1041@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome