Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1315236

Re: [PATCH 0/6] perf core: Read from overwrite ring buffer

From Alexei Starovoitov <alexei.starovoitov@gmail.com>
Newsgroups linux.kernel
Subject Re: [PATCH 0/6] perf core: Read from overwrite ring buffer
Date 2016-01-22 20:40 +0100
Message-ID <qTPIR-6m-1@gated-at.bofh.it> (permalink)
References <qTIR3-3TR-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Jan 22, 2016 at 12:13:48PM +0000, Wang Nan wrote:
> This is v2 of this series.
> 
> Compare with v1:
> 
> Fixes several bugs in v1.
> 
> Corresponsing perf has finished and can be found from:
> 
>  https://git.kernel.org/cgit/linux/kernel/git/pi3orama/linux.git/ 
>  branch: perf/overwrite-benchmark
> 
> Some benchmarking results can be found from [1].
> 
> Summary:
> 
> On a PC with Intel E5-2640 0 @ 2.50GHz CPU, execute close(-1) 3000000
> times, capture raw_syscalls:* with perf into overwrite ring buffer,
> check total time (in us):
> 
>              MEAN           STDVAR
> BASE     :  879870.81      11913.13
> RAWPERF  : 2603854.7      706658.4
> WRTBKWRD : 2313301.220      6727.957
> TAILSIZE : 2383051.860      5248.061
> RAWOVWRT : 2315273.180      5221.025
> RAWOVWRT*: 2323970.45       5103.39 
> 
> Where:
> BASE: don't use perf at all.
> RAWPERF: use non-overwrite ring buffer, perf collects all data,
> 	 write to /dev/null
> WRTBKWRD: Use backward writing ring buffer, write from tail to head,
>           never wakeup perf, collect data when exiting.
> TAILSIZE: Use tailsize ring buffer, pad 8 bytes for the size of the
>           record for each event, never wakeup perf, collect data when
> 	  exiting.
> RAWOVWRT: Use raw overwrite ring buffer, never wakeup perf, don't
>           collect data at all.
> RAWOVWRT*: Same as RAWOVWRT, without this patchset.
> 
> The benchmarking results shows WRTBKWRD is good enough. I suggest not
> to implement TAILSIZE and tail-header ring buffer.

yes. just drop patch 6.

> I will post the result on a smartphone next week.

great. would be interesting comparison.
overall I think it looks good.

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

[PATCH 0/6] perf core: Read from overwrite ring buffer Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
  [PATCH 6/6] perf core: Put size of a sample at the end of it by PERF_SAMPLE_TAILSIZE Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
  [PATCH 3/6] perf core: Prepare writing into ring buffer from end Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
  [PATCH 4/6] perf core: Add backward attribute to perf event Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
  [PATCH 2/6] perf core: Set event's default overflow_handler Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
  [PATCH 1/6] perf core: Introduce new ioctl options to pause and resume ring buffer Wang Nan <wangnan0@huawei.com> - 2016-01-22 13:20 +0100
    Re: [PATCH 1/6] perf core: Introduce new ioctl options to pause and  resume ring buffer Alexei Starovoitov <alexei.starovoitov@gmail.com> - 2016-01-22 20:40 +0100
  Re: [PATCH 0/6] perf core: Read from overwrite ring buffer Alexei Starovoitov <alexei.starovoitov@gmail.com> - 2016-01-22 20:40 +0100

csiph-web