From: "Wangnan (F)" <wangnan0@huawei.com>
To: <peterz@infradead.org>
Cc: <alexei.starovoitov@gmail.com>, <acme@kernel.org>,
<linux-kernel@vger.kernel.org>, He Kuang <hekuang@huawei.com>,
"Alexei Starovoitov" <ast@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Brendan Gregg <brendan.d.gregg@gmail.com>,
Jiri Olsa <jolsa@kernel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Namhyung Kim <namhyung@kernel.org>, Zefan Li <lizefan@huawei.com>,
<pi3orama@163.com>
Subject: Re: [PATCH 0/5] perf core: Read from overwrite ring buffer
Date: Tue, 26 Jan 2016 16:26:48 +0800 [thread overview]
Message-ID: <56A72DC8.2090306@huawei.com> (raw)
In-Reply-To: <1453710833-2865-1-git-send-email-wangnan0@huawei.com>
Hi Peter,
Do you have any further comments about this patchset? What should be
the correct route for them to be merged into mainline?
Thank you.
On 2016/1/25 16:33, Wang Nan wrote:
> This is the v3 of this series. Compare with v2, tailsize method is
> removed, ioctl command PERF_EVENT_IOC_PAUSE_OUTPUT is changed to
> _IOW('$', 9, __u32) since it has an input value, commit message
> is slightly adjusted.
>
> New test result on ARM64 is below (x86_64 result is copied from previous
> email, test method is described in previous version [1]):
>
> x86_64 | ARM64
> -----------------------+---------------------
> MEAN STDVAR | MEAN STDVAR
> BASE : 879870.81 11913.13 | 808302.67 6951.47
> RAWPERF : 2603854.70 706658.40 | 3461675.12 54075.69
> WRTBKWRD : 2313301.22 6727.96 | 3350177.98 23125.48
> TAILSIZE : 2383051.86 5248.06 | 3556496.56 24802.17
> RAWOVWRT : 2315273.18 5221.03 | 3458767.49 41560.32
> RAWOVWRT*: 2323970.45 5103.39 | 3438967.06 34095.83
>
> ARM64 platform is a smartphone with 8 Hisilicon arm64 cores
> (big/little).
>
> Benckmarking result on both architechure support removing tailsize
> method because its performance penalty is higher than WRTBKWRD. Also, it
> seems we don't need to consider tailheader method (putting whole header
> at the end of records, kernel write to the ring buffer from beginning to
> end), because the above result shows WRTBKWRD and RAWOVWRT are similar,
> and tailheader is impossible to outperform RAWOVWRT in theory.
>
> [1] http://lkml.kernel.org/g/1453464834-233200-1-git-send-email-wangnan0@huawei.com
>
> Wang Nan (5):
> perf core: Introduce new ioctl options to pause and resume ring buffer
> perf core: Set event's default overflow_handler
> perf core: Prepare writing into ring buffer from end
> perf core: Add backward attribute to perf event
> perf core: Reduce perf event output overhead by new overflow handler
>
> include/linux/perf_event.h | 22 +++++++++++--
> include/uapi/linux/perf_event.h | 4 ++-
> kernel/events/core.c | 73 +++++++++++++++++++++++++++++++++++------
> kernel/events/internal.h | 11 +++++++
> kernel/events/ring_buffer.c | 63 +++++++++++++++++++++++++++++++----
> 5 files changed, 153 insertions(+), 20 deletions(-)
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: He Kuang <hekuang@huawei.com>
> Cc: Alexei Starovoitov <ast@kernel.org>
> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Cc: Brendan Gregg <brendan.d.gregg@gmail.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Zefan Li <lizefan@huawei.com>
> Cc: pi3orama@163.com
>
prev parent reply other threads:[~2016-01-26 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 8:33 Wang Nan
2016-01-25 8:33 ` [PATCH 1/5] perf core: Introduce new ioctl options to pause and resume " Wang Nan
2016-01-25 8:33 ` [PATCH 2/5] perf core: Set event's default overflow_handler Wang Nan
2016-01-25 8:33 ` [PATCH 3/5] perf core: Prepare writing into ring buffer from end Wang Nan
2016-01-25 8:33 ` [PATCH 4/5] perf core: Add backward attribute to perf event Wang Nan
2016-01-25 8:33 ` [PATCH 5/5] perf core: Reduce perf event output overhead by new overflow handler Wang Nan
2016-01-26 0:24 ` [PATCH 0/5] perf core: Read from overwrite ring buffer Alexei Starovoitov
2016-01-26 8:26 ` Wangnan (F) [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=56A72DC8.2090306@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=brendan.d.gregg@gmail.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pi3orama@163.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
Powered by JetHome