lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 14 Dec 2020 10:28:28 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     Alexander Antonov <alexander.antonov@...ux.intel.com>
Cc:     linux-kernel@...r.kernel.org, jolsa@...hat.com,
        alexander.shishkin@...ux.intel.com, mark.rutland@....com,
        namhyung@...nel.org, mingo@...hat.com, peterz@...radead.org,
        ak@...ux.intel.com, Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH 0/5] perf stat: Introduce --iiostat mode to provide I/O
 performance metrics

Em Thu, Dec 10, 2020 at 12:03:35PM +0300, Alexander Antonov escreveu:
> Mode is intended to provide four I/O performance metrics in MB per each
> IIO stack:
>  - Inbound Read: I/O devices below IIO stack read from the host memory
>  - Inbound Write: I/O devices below IIO stack write to the host memory
>  - Outbound Read: CPU reads from I/O devices below IIO stack
>  - Outbound Write: CPU writes to I/O devices below IIO stack
> 
> Each metric requiries only one IIO event which increments at every 4B
> transfer in corresponding direction. The formulas to compute metrics
> are generic:
>     #EventCount * 4B / (1024 * 1024)
> 
> Note: --iiostat introduces new perf data aggregation mode - per I/O stack
> hence -e and -M options are not supported.
> 
> Usage examples:

My first thought was: Why not have a 'perf iiostat' subcommand?

You're reusing the aggregation code for 'perf stat' and for that I'd
love to have Ian, Andi, Jiri et all to look at how you implemented it,
but I think having a shorter way of using this would be interesting :-)

- Arnaldo
 
> 1. List all IIO stacks (example for 2-S platform):
>    $ perf stat --iiostat=show

  Would be:

     $ perf iiostat show

>    S0-uncore_iio_0<0000:00>
>    S1-uncore_iio_0<0000:80>
>    S0-uncore_iio_1<0000:17>
>    S1-uncore_iio_1<0000:85>
>    S0-uncore_iio_2<0000:3a>
>    S1-uncore_iio_2<0000:ae>
>    S0-uncore_iio_3<0000:5d>
>    S1-uncore_iio_3<0000:d7>
> 
> 2. Collect metrics for all I/O stacks:
>    $ perf stat --iiostat -- dd if=/dev/zero of=/dev/nvme0n1 bs=1M oflag=direct

     $ perf iiostat -- dd if=/dev/zero of=/dev/nvme0n1 bs=1M oflag=direct

>    357708+0 records in
>    357707+0 records out
>    375083606016 bytes (375 GB, 349 GiB) copied, 215.974 s, 1.7 GB/s
> 
>     Performance counter stats for 'system wide':
> 
>       port             Inbound Read(MB)    Inbound Write(MB)    Outbound Read(MB)   Outbound Write(MB) 
>    0000:00                    1                    0                    2                    3 
>    0000:80                    0                    0                    0                    0 
>    0000:17               352552                   43                    0                   21 
>    0000:85                    0                    0                    0                    0 
>    0000:3a                    3                    0                    0                    0 
>    0000:ae                    0                    0                    0                    0 
>    0000:5d                    0                    0                    0                    0 
>    0000:d7                    0                    0                    0                    0
> 
> 3. Collect metrics for comma separated list of I/O stacks:
>    $ perf stat --iiostat=0000:17,0:3a -- dd if=/dev/zero of=/dev/nvme0n1 bs=1M oflag=direct

     $ perf iiostat 0000:17,0:3a -- dd if=/dev/zero of=/dev/nvme0n1 bs=1M oflag=direct

>    357708+0 records in
>    357707+0 records out
>    375083606016 bytes (375 GB, 349 GiB) copied, 197.08 s, 1.9 GB/s
> 
>     Performance counter stats for 'system wide':
> 
>       port             Inbound Read(MB)    Inbound Write(MB)    Outbound Read(MB)   Outbound Write(MB) 
>    0000:17               358559                   44                    0                   22 
>    0000:3a                    3                    2                    0                    0 
> 
>         197.081983474 seconds time elapsed
> 
> Alexander Antonov (5):
>   perf stat: Add AGGR_IIO_STACK mode
>   perf evsel: Introduce an observed performance device
>   perf stat: Basic support for iiostat in perf stat
>   perf stat: Helper functions for IIO stacks list in iiostat mode
>   perf stat: Enable --iiostat mode for x86 platforms
> 
>  tools/perf/Documentation/perf-stat.txt        |  31 ++
>  tools/perf/arch/x86/util/Build                |   1 +
>  tools/perf/arch/x86/util/iiostat.c            | 460 ++++++++++++++++++
>  tools/perf/builtin-stat.c                     |  38 +-
>  tools/perf/util/evsel.h                       |   1 +
>  tools/perf/util/iiostat.h                     |  33 ++
>  .../scripting-engines/trace-event-python.c    |   2 +-
>  tools/perf/util/stat-display.c                |  51 +-
>  tools/perf/util/stat-shadow.c                 |  11 +-
>  tools/perf/util/stat.c                        |   3 +-
>  tools/perf/util/stat.h                        |   2 +
>  11 files changed, 625 insertions(+), 8 deletions(-)
>  create mode 100644 tools/perf/arch/x86/util/iiostat.c
>  create mode 100644 tools/perf/util/iiostat.h
> 
> 
> base-commit: 644bf4b0f7acde641d3db200b4db66977e96c3bd
> -- 
> 2.19.1
> 

-- 

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ