mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Fix an error on perf-bench document
Date: Tue, 19 Jun 2012 17:48:44 +0900	[thread overview]
Message-ID: <87mx3zhekz.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20120618090501.GB28824@gmail.com> (Ingo Molnar's message of "Mon, 18 Jun 2012 11:05:01 +0200")

Hi, Ingo

On Mon, 18 Jun 2012 11:05:01 +0200, Ingo Molnar wrote:
> There's several typos all across the perf bench documentation:
>
> 1)
>
>        This perf bench command is general framework for benchmark suites.
>
> s/is general/is a general
>

Will fix.


> 2)
>
> The output of 'perf bench --help' outputs weird looking 
> formatting characters like:
>
>            .ft C
>            % perf bench sched pipe                      # with no style specified
>            (executing 1000000 pipe operations between two tasks)
>                    Total time:5.855 sec
>                            5.855061 usecs/op
>                            170792 ops/sec
>            .ft
>

I have no idea on this, maybe a problem of asciidoc?


> 3)
>
> This:
>
>            all: test all suite (pseudo suite)
>
> s/all suite (psudo suite)/all benchmark suites
>
> (this should be fixed for perf bench mem as well.)
>

Will fix.


> 4)
>
> perf bench mem memcpy -h outputs:
>
>     -l, --length <1MB>    Specify length of memory to copy. available unit: B, MB, GB (upper and lower)
>
> bad capitalization: s/. a/. A
>
> s/unit/units
>

Will fix too.


> 5)
>
> This:
>
>     -c, --clock           Use CPU clock for measuring
>
> should probably clarify why the CPU clock matters and what 
> measurement is done otherwise.
>

This looks a bit weird. If -c switch was given, it'd use the cycles
event not the cpu-clock event. If omitted, it'd use the gtod().

Thanks,
Namhyung

  reply	other threads:[~2012-06-19  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 14:55 Namhyung Kim
2012-06-18  9:05 ` Ingo Molnar
2012-06-19  8:48   ` Namhyung Kim [this message]
2012-06-24 15:59     ` Hitoshi Mitake
2012-06-27 14:28       ` Hitoshi Mitake
2012-06-28  1:56         ` Namhyung Kim
2012-07-01 15:05           ` 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=87mx3zhekz.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.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

all inboxes | Powered by JetHome®