public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stanislav Fomichev <stfomichev@yandex-team.ru>
Cc: acme@kernel.org, artagnon@gmail.com, jolsa@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] perf timechart: add more options to IO mode
Date: Thu, 12 Jun 2014 10:03:39 +0900	[thread overview]
Message-ID: <87lht39bx0.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1402412694-5996-4-git-send-email-stfomichev@yandex-team.ru> (Stanislav Fomichev's message of "Tue, 10 Jun 2014 19:04:54 +0400")

On Tue, 10 Jun 2014 19:04:54 +0400, Stanislav Fomichev wrote:
> --io-skip-eagain - don't show EAGAIN errors
> --io-min-time    - make small io bursts visible
> --io-merge-dist  - merge adjacent events
>
> Signed-off-by: Stanislav Fomichev <stfomichev@yandex-team.ru>
> ---
>  tools/perf/Documentation/perf-timechart.txt |  9 ++++++
>  tools/perf/builtin-timechart.c              | 49 +++++++++++++++++++++++++++--
>  2 files changed, 56 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-timechart.txt b/tools/perf/Documentation/perf-timechart.txt
> index ec6b46c7bca0..62c29656ad95 100644
> --- a/tools/perf/Documentation/perf-timechart.txt
> +++ b/tools/perf/Documentation/perf-timechart.txt
> @@ -64,6 +64,15 @@ TIMECHART OPTIONS
>  	duration or tasks with given name. If number is given it's interpreted
>  	as number of nanoseconds. If non-numeric string is given it's
>  	interpreted as task name.
> +--io-skip-eagain::
> +	Don't draw EAGAIN IO events.
> +--io-min-time::
> +	Draw small events as if they lasted min-time. Useful when you need
> +	to see very small and fast IO. Default value is 1ms.

It's in nano-second unit, right?  If so, it's very unconvenient for user
to specify.  Maybe we could support to parse unit (s, ms, us, ...) also.


> +--io-merge-dist::
> +	Merge events that are merge-dist nanoseconds apart.
> +	Reduces number of figures on the SVG and makes it more render-friendly.
> +	Default value is 1us.

Ditto.

Thanks,
Namhyung

  reply	other threads:[~2014-06-12  1:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 15:04 [PATCH v2 0/3] perf timechart io mode Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 1/3] perf timechart: implement IO mode Stanislav Fomichev
2014-06-12  0:59   ` Namhyung Kim
2014-06-16  6:08     ` Stanislav Fomichev
2014-06-18  0:31       ` Namhyung Kim
2014-06-18  9:00         ` Stanislav Fomichev
2014-06-19  0:30           ` Namhyung Kim
2014-06-19  9:58             ` Stanislav Fomichev
2014-06-19 12:18               ` Stanislav Fomichev
2014-06-19 12:38                 ` Namhyung Kim
2014-06-10 15:04 ` [PATCH 2/3] perf timechart: conditionally update start_time on fork Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 3/3] perf timechart: add more options to IO mode Stanislav Fomichev
2014-06-12  1:03   ` Namhyung Kim [this message]
2014-06-16  6:15     ` Stanislav Fomichev
2014-06-18  0:33       ` Namhyung Kim
  -- strict thread matches above, loose matches on Subject: below --
2014-06-19 12:23 [PATCH v3 0/3] perf timechart io mode Stanislav Fomichev
2014-06-19 12:23 ` [PATCH 3/3] perf timechart: add more options to IO mode Stanislav Fomichev

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=87lht39bx0.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=artagnon@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stfomichev@yandex-team.ru \
    /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