From: Darren Hart <dvhart@linux.intel.com>
To: Hitoshi Mitake <h.mitake@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Michel Lespinasse <walken@google.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] perf bench: add new benchmark subsystem and suite "futex wait"
Date: Tue, 05 Jun 2012 11:17:08 -0700 [thread overview]
Message-ID: <4FCE4D24.5040307@linux.intel.com> (raw)
In-Reply-To: <CAMO-S2gyzK3VTQcTRw+FAO9ui_gy=1z=MVxUYM9sPN51KrDgkg@mail.gmail.com>
On 05/20/2012 02:37 AM, Hitoshi Mitake wrote:
> On Sun, May 20, 2012 at 5:32 PM, Hitoshi Mitake <h.mitake@gmail.com> wrote:
>> On Fri, May 18, 2012 at 1:24 AM, Darren Hart <dvhart@linux.intel.com> wrote:
>>> On 05/17/2012 08:21 AM, Hitoshi Mitake wrote:
>>>> Hi Ingo, Eric and Darren,
>>>> (CCed perf and futex folks)
>>>>
>>>> I wrote this patch for adding new subsystem "futex" and its suite "wait" to perf
>>>> bench on tip/master. This is based on futextest by Darren Hart.
>>>>
>>>> Could you allow me to import your source code of futextest to perf bench, Darren?
>>>>
>>>
>>> I do have some concerns I'd like to address first.
>>>
>>> What is advantage of incorporating this into perf as opposed to running
>>> it with perf?
>>
>> The main and direct advantage is that perf bench can share useful
>> utilities stored under tools/perf/util/ directory e.g. parse-options[ch].
>>
>
> BTW, I often feel parse-options.[ch] of perf (this was come from git,
> right?) is very useful not only for perf and git but also other
> projects. So I think these stuff are worth independence as a
> library. If the library contains unified feature for parsing and
> evaluating configuration files, the hell of managing configurable
> options will be reduced. e.g. I often use "strace -e open <command>"
> to detect configuration files read by the <command>...
>
> I thought that if perf bench can be independent from perf with such
> efforts, it can be smaller sized and statically linked binary. From my
> experience, this will be good for embedded systems people.
>
> This independence also has risk: less people can find it or is
> attracted even if it stays in the kernel tree (e.g. tools/bench/). But
> it seems that very few people know about perf bench, so this will not
> be a serious problem ;)
>
> I'd like to hear your opinion.
I haven't been involved with perf tools/bench so I haven't really formed
an opinion. Ingo and Arnaldo, would either of you care to weigh in on
the pros/cons of merging futextest into perf?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-05 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 15:21 [PATCH] perf bench: add new benchmark subsystem and suite "futex wait" Hitoshi Mitake
2012-05-17 16:24 ` Darren Hart
2012-05-20 8:32 ` Hitoshi Mitake
2012-05-20 9:37 ` Hitoshi Mitake
2012-06-05 18:17 ` Darren Hart [this message]
2012-06-06 7:39 ` Ingo Molnar
2012-06-06 12:30 ` Arnaldo Carvalho de Melo
2012-06-06 15:37 ` Ingo Molnar
2012-06-06 14:18 ` David Ahern
2012-06-06 16:02 ` Hitoshi Mitake
2012-06-07 15:11 ` Hitoshi Mitake
2012-06-13 16:51 ` Darren Hart
2012-06-24 16:08 ` Hitoshi Mitake
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=4FCE4D24.5040307@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=eric.dumazet@gmail.com \
--cc=h.mitake@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
--cc=walken@google.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.