mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 1/3] perf callchain: Convert children list to rbtree
Date: Mon, 23 Sep 2013 11:36:45 +0200	[thread overview]
Message-ID: <20130923093645.GA1025@krava.brq.redhat.com> (raw)
In-Reply-To: <87zjr3q42c.fsf@sejong.aot.lge.com>

On Mon, Sep 23, 2013 at 06:29:15PM +0900, Namhyung Kim wrote:
> Hi,
> 
> On Sun, 22 Sep 2013 13:15:59 +0200, Jiri Olsa wrote:
> > On Tue, Sep 10, 2013 at 05:24:16PM +0900, Namhyung Kim wrote:
> >> From: Namhyung Kim <namhyung.kim@lge.com>
> >
> > SNIP
> >
> >> index 2b585bc308cf..1b22b6269213 100644
> >> --- a/tools/perf/util/callchain.h
> >> +++ b/tools/perf/util/callchain.h
> >> @@ -21,10 +21,9 @@ enum chain_order {
> >>  
> >>  struct callchain_node {
> >>  	struct callchain_node	*parent;
> >> -	struct list_head	siblings;
> >> -	struct list_head	children;
> >>  	struct list_head	val;
> >>  	struct rb_node		rb_node; /* to sort nodes in an rbtree */
> >> +	struct rb_root		rb_root_in; /* sorted tree of children */
> >>  	struct rb_root		rb_root; /* sorted tree of children */
> >>  	unsigned int		val_nr;
> >>  	u64			hit;
> >> @@ -86,8 +85,6 @@ extern __thread struct callchain_cursor callchain_cursor;
> >>  
> >>  static inline void callchain_init(struct callchain_root *root)
> >>  {
> >> -	INIT_LIST_HEAD(&root->node.siblings);
> >> -	INIT_LIST_HEAD(&root->node.children);
> >>  	INIT_LIST_HEAD(&root->node.val);
> >
> > don't we miss rb_root_in init here, like:
> >
> > 	root->node.rb_root_in = RB_ROOT;
> 
> The struct callchain_root in hist entry initialized to zero so
> technically it doesn't need to be set.  But I think it's better to have
> explicit initializer.

yep, I was writing some tests for this when I noticed that,
having callchain_root defined on stack

jirka

  reply	other threads:[~2013-09-23  9:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10  8:24 [PATCH 0/3] perf tools: Fix scalability problem on callchain merging Namhyung Kim
2013-09-10  8:24 ` [PATCH 1/3] perf callchain: Convert children list to rbtree Namhyung Kim
2013-09-10  9:02   ` Namhyung Kim
2013-09-10  9:52   ` Jiri Olsa
2013-09-10 10:25     ` Ingo Molnar
2013-09-10 11:34       ` Frederic Weisbecker
2013-09-22 11:15   ` Jiri Olsa
2013-09-23  9:29     ` Namhyung Kim
2013-09-23  9:36       ` Jiri Olsa [this message]
2013-09-10  8:24 ` [PATCH 2/3] perf ui/progress: Add new helper functions for progress bar Namhyung Kim
2013-09-10  8:24 ` [PATCH 3/3] perf tools: Show progress on histogram collapsing Namhyung Kim
2013-09-10 11:58 ` [PATCH 0/3] perf tools: Fix scalability problem on callchain merging Frederic Weisbecker

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=20130923093645.GA1025@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=torvalds@linux-foundation.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