public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Andi Kleen <andi@firstfloor.org>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly
Date: Thu, 7 Jan 2016 08:43:35 +0900	[thread overview]
Message-ID: <20160106234335.GE8053@sejong> (raw)
In-Reply-To: <20160106233149.GE2012@kernel.org>

On Wed, Jan 06, 2016 at 08:31:49PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jan 07, 2016 at 08:26:45AM +0900, Namhyung Kim escreveu:
> > On Wed, Jan 06, 2016 at 08:06:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Wed, Jan 06, 2016 at 09:54:59AM +0900, Namhyung Kim escreveu:
> > > > Currently, the dynamic sort keys compares trace data using memcmp().
> > > > But for output sorting, it should check data size and compare by word.
> > > > Also it sorted strings in reverse order, fix it.
> > > 
> > > Can this be broken down in two patches? This is complex code, lets try
> > > to make it as bisectable as possible.
> > 
> > OK, I'll break out the string part then.  But I think it doesn't help
> > much to reduce the complexity.
> 
> Well, number of patches is not a problem, everytime I see a "Also lets
> do this other thing" I cringe, it is automatic, sorry :-\
> 
> For reviewing its soooo much better to see things nicely separated, and
> sometimes I like one part but not the other, so I pick one and continue
> discussion on the other, etc.

OK, I understand your concern.  I'll try to make it more easier to review.

Thanks,
Namhyung


> > > 
> > > > 
> > > > Before)
> > > > 
> > > >   $ perf report -F overhead -s prev_pid,next_pid
> > > >   ...
> > > >   # Overhead    prev_pid    next_pid
> > > >   # ........  ..........  ..........
> > > >   #
> > > >        0.39%         490           0
> > > >        9.12%         225           0
> > > >        0.04%         224           0
> > > >        0.51%         731         189
> > > >        0.08%         731           3
> > > >        0.12%         731           0
> > > >        4.82%         729           0
> > > >        0.08%        1229           0
> > > >        0.20%         715           0
> > > >        4.78%         189         225
> > > >   ...
> > > > 
> > > > After)
> > > > 
> > > >   $ perf report -F overhead -s prev_pid,next_pid
> > > >   ...
> > > >   # Overhead    prev_pid    next_pid
> > > >   # ........  ..........  ..........
> > > >   #
> > > >        0.43%           0           7
> > > >        0.04%           0          11
> > > >        0.04%           0          12
> > > >        0.08%           0          14
> > > >        0.04%           0          17
> > > >        0.08%           0          19
> > > >        0.04%           0          22
> > > >        0.04%           0          27
> > > >        0.04%           0          37
> > > >        0.04%           0          42
> > > >   ...
> > > > 
> > > > Reported-by: Arnaldo Carvalho de Melo <acme@kernel.org>
> > > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > > > ---
> > > >  tools/perf/util/sort.c | 47 ++++++++++++++++++++++++++++++++++++++++++++++-
> > > >  1 file changed, 46 insertions(+), 1 deletion(-)
> > > > 
> > > > diff --git a/tools/perf/util/sort.c b/tools/perf/util/sort.c
> > > > index 9618a64875c0..264d2b630549 100644
> > > > --- a/tools/perf/util/sort.c
> > > > +++ b/tools/perf/util/sort.c
> > > > @@ -1798,6 +1798,51 @@ static int64_t __sort__hde_cmp(struct perf_hpp_fmt *fmt,
> > > >  	return memcmp(a->raw_data + offset, b->raw_data + offset, size);
> > > >  }
> > > >  
> > > > +static int64_t __sort__hde_sort(struct perf_hpp_fmt *fmt,
> > > > +				struct hist_entry *a, struct hist_entry *b)
> > > > +{
> > > > +	struct hpp_dynamic_entry *hde;
> > > > +	struct format_field *field;
> > > > +	unsigned offset, size;
> > > > +	int64_t *a64, *b64;
> > > > +	int32_t *a32, *b32;
> > > > +	int16_t *a16, *b16;
> > > > +
> > > > +	hde = container_of(fmt, struct hpp_dynamic_entry, hpp);
> > > > +
> > > > +	field = hde->field;
> > > > +	if (field->flags & FIELD_IS_DYNAMIC) {
> > > > +		unsigned long long dyn;
> > > > +
> > > > +		pevent_read_number_field(field, a->raw_data, &dyn);
> > > > +		offset = dyn & 0xffff;
> > > > +		size = (dyn >> 16) & 0xffff;
> > > > +	} else {
> > > > +		offset = field->offset;
> > > > +		size = field->size;
> > > > +	}
> > > > +
> > > > +	if (field->flags & FIELD_IS_STRING)
> > > > +		return strcmp(b->raw_data + offset, a->raw_data + offset);
> > > > +
> > > > +	switch (size) {
> > > > +	case 8:
> > > > +		a64 = a->raw_data + offset;
> > > > +		b64 = b->raw_data + offset;
> > > > +		return *b64 - *a64;
> > > > +	case 4:
> > > > +		a32 = a->raw_data + offset;
> > > > +		b32 = b->raw_data + offset;
> > > > +		return *b32 - *a32;
> > > > +	case 2:
> > > > +		a16 = a->raw_data + offset;
> > > > +		b16 = b->raw_data + offset;
> > > > +		return *b16 - *a16;
> > > > +	default:
> > > > +		return memcmp(b->raw_data + offset, a->raw_data + offset, size);
> > > > +	}
> > > > +}
> > > > +
> > > >  bool perf_hpp__is_dynamic_entry(struct perf_hpp_fmt *fmt)
> > > >  {
> > > >  	return fmt->cmp == __sort__hde_cmp;
> > > > @@ -1826,7 +1871,7 @@ __alloc_dynamic_entry(struct perf_evsel *evsel, struct format_field *field)
> > > >  
> > > >  	hde->hpp.cmp = __sort__hde_cmp;
> > > >  	hde->hpp.collapse = __sort__hde_cmp;
> > > > -	hde->hpp.sort = __sort__hde_cmp;
> > > > +	hde->hpp.sort = __sort__hde_sort;
> > > >  
> > > >  	INIT_LIST_HEAD(&hde->hpp.list);
> > > >  	INIT_LIST_HEAD(&hde->hpp.sort_list);
> > > > -- 
> > > > 2.6.4

  reply	other threads:[~2016-01-06 23:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06  0:54 [PATCH v3 1/5] perf tools: Add all matching dynamic sort keys for field name Namhyung Kim
2016-01-06  0:54 ` [PATCH v3 2/5] perf tools: Add document for dynamic sort keys Namhyung Kim
2016-01-06  0:54 ` [PATCH v3 3/5] perf tools: Fix dynamic sort keys to sort properly Namhyung Kim
2016-01-06 23:06   ` Arnaldo Carvalho de Melo
2016-01-06 23:26     ` Namhyung Kim
2016-01-06 23:31       ` Arnaldo Carvalho de Melo
2016-01-06 23:43         ` Namhyung Kim [this message]
2016-01-06 23:50         ` Arnaldo Carvalho de Melo
2016-01-07  0:07           ` Namhyung Kim
2016-01-06  0:55 ` [PATCH v3 4/5] perf tools: Support dynamic sort keys for -F/--fields Namhyung Kim
2016-01-06  0:55 ` [PATCH v3 5/5] perf evlist: Add --trace-fields option to show trace fields Namhyung Kim
2016-01-06 23:10   ` Arnaldo Carvalho de Melo
2016-01-06 23:21     ` Namhyung Kim
2016-01-06 23:29       ` Arnaldo Carvalho de Melo
2016-01-06 23:42         ` Namhyung Kim
2016-01-06 11:19 ` [PATCH v3 1/5] perf tools: Add all matching dynamic sort keys for field name Jiri Olsa
2016-01-06 16:29   ` Arnaldo Carvalho de Melo
2016-01-06 23:09     ` Namhyung Kim

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=20160106234335.GE8053@sejong \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=wangnan0@huawei.com \
    /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