linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Frank Rowand <frank.rowand@am.sony.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	williams@redhat.com, jkacur@redhat.com
Subject: Re: [PATCH] rt-tests: incorrect first latency value for --verbose option
Date: Mon, 7 May 2012 23:41:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1205072322250.3886@tycho> (raw)
In-Reply-To: <4FA1CB20.5000209@am.sony.com>



On Wed, 2 May 2012, Frank Rowand wrote:

> 
> When the --verbose option is selected, the first value for each thread is
> incorrectly reported as zero.
> 
> This is because when collecting the first value, the index into stat->values is
> incremented from zero to one before storing the value.  But when printing the
> values, the first value printed is stat->values[0], which has been initialized
> to zero.

Hi Frank

Ok, no more posting from me after winning a bottle of whiskey at the Irish 
Pub on quiz night. :)

I've been looking at this one, and I'm not sure about it.
According to the help output, 

"-v       --verbose         output values on stdout for statistics
                           format: n:c:v n=tasknum c=count v=value in us"

./cyclictest --verbose -p99 -t | awk '$2~/^0/{ print }' 

       0:       0:       0
       1:       0:       0
       2:       0:       0
       3:       0:       0
       4:       0:       0
       5:       0:       0
       6:       0:       0
       7:       0:       0

So, it looks like the values are 0 at count 0, doesn't that make sense?

Thanks

John Kacur

  reply	other threads:[~2012-05-07 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  0:02 [PATCH] rt-tests: incorrect first latency value for --verbose option Frank Rowand
2012-05-07 21:41 ` John Kacur [this message]
2012-05-07 21:45   ` Frank Rowand
2012-05-07 22:03     ` John Kacur
2012-05-07 22:13       ` Frank Rowand

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=alpine.LFD.2.02.1205072322250.3886@tycho \
    --to=jkacur@redhat.com \
    --cc=frank.rowand@am.sony.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@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;
as well as URLs for NNTP newsgroup(s).