From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Andi Kleen <ak@linux.intel.com>,
jolsa@redhat.com, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 0/7] tools/perf: Update rbtree implementation and optimize users
Date: Mon, 27 Nov 2017 14:14:22 -0300 [thread overview]
Message-ID: <20171127171422.GB3298@kernel.org> (raw)
In-Reply-To: <20171127161457.3gqxg2ex67whxtwu@linux-n805>
Em Mon, Nov 27, 2017 at 08:14:57AM -0800, Davidlohr Bueso escreveu:
> On Sun, 26 Nov 2017, Andi Kleen wrote:
>
> > > Applies on today's -tip tree. Please consider for v4.16.
> >
> > No numbers on the improvements?
>
> I have not done performance tests perse for perf, but ultimately
> it will depend a lot on the workload and size of the tree. I had
> previously measured, on a Xeon E5-2450 @ 2.10GHz, the cost of
> an rb_first() was ~60 cycles for 100 nodes, and ~75 cycles with
> 1000 nodes. fwiw.
I'll try to do some before/after perf stat runs to compare output and to
see the overall diff in cycles, etc.
- Arnaldo
prev parent reply other threads:[~2017-11-27 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 2:30 [PATCH -tip 0/7] tools/perf: Update rbtree implementation and optimize users Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 1/7] tools/perf: Update rbtree implementation Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 2/7] perf machine: Use cached rbtrees Davidlohr Bueso
2018-01-04 5:51 ` [lkp-robot] [perf machine] 8edf8850d5: stderr./usr/src/linux-perf-x86_64-rhel-#/tools/perf/util/rb_resort.h:#:#:error:passing_argument#of'threads_sorted__new'from_incompatible_pointer_type[-Werror=incompatible-pointer-types] kernel test robot
2018-01-04 5:51 ` kernel test robot
2018-01-05 17:04 ` Davidlohr Bueso
2018-01-05 17:04 ` Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 3/7] perf callchain: Use cached rbtrees Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 4/7] perf util: Use cached rbtree for rblists Davidlohr Bueso
2018-01-30 2:41 ` [lkp-robot] [perf util] f7a7a64385: stderr.builtin-trace.c:#:#:note:in_expansion_of_macro'DECLARE_RESORT_RB_INTLIST' kernel test robot
2017-11-27 2:30 ` [PATCH 5/7] perf symbols: Use cached rbtrees Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 6/7] perf hist: " Davidlohr Bueso
2017-11-27 2:30 ` [PATCH 7/7] perf sched: " Davidlohr Bueso
2017-11-27 6:06 ` [PATCH -tip 0/7] tools/perf: Update rbtree implementation and optimize users Andi Kleen
2017-11-27 16:14 ` Davidlohr Bueso
2017-11-27 17:14 ` Arnaldo Carvalho de Melo [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=20171127171422.GB3298@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.